S everity Levels and Response Times Sample Clauses

S everity Levels and Response Times. The following are a description of the service levels and the service level response times:
AutoNDA by SimpleDocs

Related to S everity Levels and Response Times

  • Response Times Qubit bases its response times and the actions it takes to resolve problems on an assessment of the impact of the reported technical issue. The more serious the impact, the higher the assigned priority. For all support issues relating to Customer, Qubit will respond in accordance with Table 1: P1 1 hour 4 hours P2 1 hour 8 hours P3 4 hours 72 hours P4 1 business day Next or a later major release **The Priority Levels are defined in Section II(2) below.

  • Measuring EPP parameters Every 5 minutes, EPP probes will select one “IP address” of the EPP servers of the TLD being monitored and make an “EPP test”; every time they should alternate between the 3 different types of commands and between the commands inside each category. If an “EPP test” result is undefined/unanswered, the EPP service will be considered as unavailable from that probe until it is time to make a new test.

  • Response Time PROVIDING PARTY shall respond to and resolve any problems in connection with the Corporate Services for RECEIVING PARTY within a commercially reasonable period of time, using response and proposed resolution times consistent with its response and resolution of such problems for itself.

  • Staffing Levels To the extent legislative appropriations and PIN authorizations allow, safe staffing levels will be maintained in all institutions where employees have patient, client, inmate or student care responsibilities. In July of each year, the Secretary or Deputy Secretary of each agency will, upon request, meet with the Union, to hear the employees’ views regarding staffing levels. In August of each year, the Secretary or Deputy Secretary of Budget and Management will, upon request, meet with the Union to hear the employees’ views regarding the Governor’s budget request.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs. 8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.

  • Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.

  • Service Levels All service level requirements will be set forth in Exhibit A (“XXXX.xxx Referral Service Level Requirements”). Recipient Xxxxxx agrees to adhere, and encourage Recipient Agent’s adherence, with the version of the XXXX.xxx Referral Service Level Requirements in effect at the time XXXX.xxx identifies the Referral to Recipient Broker/Agent.

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