PROBLEM SEVERITY LEVELS AND RESPONSE TIME Sample Clauses

PROBLEM SEVERITY LEVELS AND RESPONSE TIME. DATA will provide support to EMC [*].
AutoNDA by SimpleDocs
PROBLEM SEVERITY LEVELS AND RESPONSE TIME. 2.1.1 DATA will provide support to EMC [*]. 2.1.2 McDATA will respond and engage [*] EMC contacting McDATA in regard to a defect. 2.1.3 The incident priority scheme described below will be used. [*]
PROBLEM SEVERITY LEVELS AND RESPONSE TIME. 3.1.1 McDATA will provide support to EMC [*]. 3.1.2 McDATA will respond and engage [*] EMC contacting McDATA in regard to a defect. 3.1.3 The incident priority scheme described below will be used. Severity Level 1: Severity Level 1 [*] Severity Level 2: Severity Level 2 [*] Severity Level 3: Severity Level 3 [*] Severity Level 4: Sevexxxx Xxxxx 0 [*] Severity Time to fix -------------------------------------------- 1 [*] ------------ ------------------------ 2 [*] ------------ ------------------------ 3 [*] ------------ ------------------------ 4 [*] ------------ ------------------------ [*] * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. Asterisks within brackets denote omission.
PROBLEM SEVERITY LEVELS AND RESPONSE TIME. 2.1.1 DATA will provide support to EMC [*]. 2.1.2 McDATA will respond and engage [*] EMC contacting McDATA in regard to a defect. 2.1.3 The incident priority scheme described below will be used. Severity Level 1: Severity Level 1 [*] Severity Level 2: Severity Level 2 [*] Severity Level 3: Sevexxxx Xxxxx 0 [*] * Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. Asterisks within brackets denote omission.
PROBLEM SEVERITY LEVELS AND RESPONSE TIME. 3.1.1 SUPPLIER will provide support to EMC [*]. 3.1.2 SUPPLIER will respond and engage within [*] of EMC contacting SUPPLIER in regard to a defect. 3.1.3 The incident priority scheme described below will be used. Severity Level 1: [*]. Severity Level 2: [*]. Severity Level 3: [*]. Severity Level 4: [*]. SUPPLIER will use its best efforts to fix Priority 1 incidents and commercially reasonable efforts for Priority 2, 3, and 4 incidents reported by EMC engineering within the times listed below: ---------------- -------------------- Severity Time to fix ================ ==================== 1 [*] ---------------- -------------------- * will be [*]

Related to PROBLEM SEVERITY LEVELS AND RESPONSE TIME

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

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

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

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

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • Business Continuity Registry Operator shall maintain a business continuity plan, which will provide for the maintenance of Registry Services in the event of an extraordinary event beyond the control of the Registry Operator or business failure of Registry Operator, and may include the designation of a Registry Services continuity provider. If such plan includes the designation of a Registry Services continuity provider, Registry Operator shall provide the name and contact information for such Registry Services continuity provider to ICANN. In the case of an extraordinary event beyond the control of the Registry Operator where the Registry Operator cannot be contacted, Registry Operator consents that ICANN may contact the designated Registry Services continuity provider, if one exists. Registry Operator shall conduct Registry Services Continuity testing at least once per year.

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

  • Designated Configuration; Trained Personnel State Street and the Fund shall be responsible for supplying, installing and maintaining the Designated Configuration at the Designated Locations. State Street and the Fund agree that each will engage or retain the services of trained personnel to enable both parties to perform their respective obligations under this Addendum. State Street agrees to use commercially reasonable efforts to maintain the System so that it remains serviceable, provided, however, that State Street does not guarantee or assure uninterrupted remote access use of the System.

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

  • Year 2000 Compatibility Take all action necessary to assure that its computer based systems are able to operate and effectively process data including dates on and after January 1, 2000, and, at the reasonable request of the Administrative Agent or the Required Lenders, provide evidence to the Lenders of such year 2000 compatibility.

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