Major Problem Sample Clauses

Major Problem. Service Provider’s responsibilities include: 1. Effectively execute Major Problem Reviews associated with all Major Incidents that arise or may arise out of the Services, in compliance with the processes defined in the Service Management Manual. 1.1. The assignment of a Problem Manager to facilitate the Major Problem Review. 1.2. An analysis of lessons learned from the Major Incident (e.g. things done well, things needing improvement, etc.). 1.3. A description of the associated Incident, including description of the failure, business impact, duration, affected systems, affected services, affected customers, work executed to Resolve the Incident, etc. 1.4. A detailed Root Cause Analysis of the Incident. 1.5. Identification of any Problem / Known Error records and/to workarounds associated with or created. 1.6. Communication of findings and outcomes to all relevant stakeholders. 1.7. The identification, documentation and submission of identified improvements. 1.8. Preventive action items tracked to completion, including regular communication with relevant stakeholders during the process. 1.9. Notice to all relevant stakeholders when preventative action items have been completed or missed.
AutoNDA by SimpleDocs
Major Problem. An issue with a Service which has widespread impact to end users but which (a) does not make the Service unusable for a large percentage of queries or operations, and (b) is an SLA violation which causes [***] of Zillow’s queries to exceed the Critical Threshold within [***]. This is otherwise known as “Major”. Major Problems are given a default Priority of “P2”. Once a Major Problem has been outstanding for more than [***], either party may, using reasonable judgment, escalate the priority to “P1” or downgrade to a lower priority issue.
Major Problem. If a Problem is a Major Problem, HNS will attempt to restore full System functionality via a software patch, by changing a database, by suggesting that Equipment components be replaced, or by some other method. HNS personnel, with TELIGENT permission, may attempt to dial in to the System to identify the cause of the Major Problem. Should a software patch, if required and requested, not be provided within [redacted] of Response and HNS cannot simulate or recreate or otherwise identify the cause of the Problem at HNS' facility, HNS will dispatch, at TELIGENT's request, a qualified maintenance engineer to travel to TELIGENT's site. The designated HNS maintenance engineer shall remain on-site and dedicated to TELIGENT until such time as the Major Problem is either resolved or downgraded to a Minor Problem. HNS' TAC will continue telephone assistance, as required, during the duration of Problem resolution. If the Major Problem resolution shows that the Problem which resulted in on-site support was not caused by Equipment or Software provided by HNS, or if HNS demonstrates that TELIGENT has not maintained the Equipment in accordance with the Documentation, or TELIGENT has not reasonably followed the System Support Services administrative and technical procedures provided by HNS, then TELIGENT will pay HNS for the site visit in accordance with HNS standard rates and any related out of pocket expenses.

Related to Major Problem

  • Year 2000 Problem The Company and its Subsidiaries have reviewed the areas within their business and operations which could be adversely affected by, and have developed or are developing a program to address on a timely basis, the "Year 2000 Problem" (that is, the risk that computer applications used by the Company and its Subsidiaries may be unable to recognize and perform properly date-sensitive functions involving certain dates prior to and any date after December 31, 1999). Based on such review and program, the Company reasonably believes that the "Year 2000 Problem" will not have a Material Adverse Effect.

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union Xxxxxxx, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.

  • Abuse, Neglect, Exploitation Grantee will; a. take all steps necessary, to protect the health, safety and welfare of its clients and participants. b. develop and implement written policies and procedures for abuse, neglect and exploitation. c. notify appropriate authorities of any allegations of abuse, neglect, or exploitation as required by 25 TAC § 448.703.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Force Majeure Event After giving effect to any applicable provision, disruption fallback or remedy specified in, or pursuant to, the relevant Confirmation or elsewhere in this Agreement, by reason of force majeure or act of state occurring after a Transaction is entered into, on any day:— (1) the Office through which such party (which will be the Affected Party) makes and receives payments or deliveries with respect to such Transaction is prevented from performing any absolute or contingent obligation to make a payment or delivery in respect of such Transaction, from receiving a payment or delivery in respect of such Transaction or from complying with any other material provision of this Agreement relating to such Transaction (or would be so prevented if such payment, delivery or compliance were required on that day), or it becomes impossible or impracticable for such Office so to perform, receive or comply (or it would be impossible or impracticable for such Office so to perform, receive or comply if such payment, delivery or compliance were required on that day); or (2) such party or any Credit Support Provider of such party (which will be the Affected Party) is prevented from performing any absolute or contingent obligation to make a payment or delivery which such party or Credit Support Provider has under any Credit Support Document relating to such Transaction, from receiving a payment or delivery under such Credit Support Document or from complying with any other material provision of such Credit Support Document (or would be so prevented if such payment, delivery or compliance were required on that day), or it becomes impossible or impracticable for such party or Credit Support Provider so to perform, receive or comply (or it would be impossible or impracticable for such party or Credit Support Provider so to perform, receive or comply if such payment, delivery or compliance were required on that day), so long as the force majeure or act of state is beyond the control of such Office, such party or such Credit Support Provider, as appropriate, and such Office, party or Credit Support Provider could not, after using all reasonable efforts (which will not require such party or Credit Support Provider to incur a loss, other than immaterial, incidental expenses), overcome such prevention, impossibility or impracticability;

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • Retainage for Unacceptable Corrective Action Plan or Plan Failure If the corrective action plan is unacceptable to the Department or Customer, or implementation of the plan fails to remedy the performance deficiencies, the Department or Customer will retain ten percent (10%) of the total invoice amount. The retainage will be withheld until the Contractor resolves the performance deficiencies. If the performance deficiencies are resolved, the Contractor may invoice the Department or Customer for the retained amount. If the Contractor fails to resolve the performance deficiencies, the retained amount will be forfeited to compensate the Department or Customer for the performance deficiencies.

  • Force Majeure Events a) Neither Party shall be responsible or liable for or deemed in breach hereof because of any delay or failure in the performance of its obligations hereunder (except for obligations to pay money due prior to occurrence of Force Majeure events under this Agreement) or failure to meet milestone dates due to any event or circumstance (a "Force Majeure Event") beyond the reasonable control of the Party experiencing such delay or failure, including the occurrence of any of the following: i) acts of God; ii) typhoons, floods, lightning, cyclone, hurricane, drought, famine, epidemic, plague or other natural calamities; iii) acts of war (whether declared or undeclared), invasion or civil unrest; iv) any requirement, action or omission to act pursuant to any judgment or order of any court or judicial authority in India (provided such requirement, action or omission to act is not due to the breach by the SPG or of any Law or any of their respective obligations under this Agreement); v) inability despite complying with all legal requirements to obtain, renew or maintain required licenses or Legal Approvals; vi) earthquakes, explosions, accidents, landslides; fire; vii) expropriation and/or compulsory acquisition of the Project in whole or in part by Government Instrumentality; viii) chemical or radioactive contamination or ionizing radiation; or ix) damage to or breakdown of transmission facilities of GETCO/ DISCOMs; x) Exceptionally adverse weather condition which are in excess of the statistical measure of the last hundred (100) years.

  • SAVINGS/FORCE MAJEURE A Force Majeure occurrence is an event or effect that cannot be reasonably anticipated or controlled and is not due to the negligence or willful misconduct of the affected party. Force Majeure includes, but is not limited to, acts of God, acts of war, acts of public enemies, terrorism, strikes, fires, explosions, actions of the elements, floods, or other similar causes beyond the control of the Contractor or the Commissioner in the performance of the Contract where non- performance, by exercise of reasonable diligence, cannot be prevented. The affected party shall provide the other party with written notice of any Force Majeure occurrence as soon as the delay is known and provide the other party with a written contingency plan to address the Force Majeure occurrence, including, but not limited to, specificity on quantities of materials, tooling, people, and other resources that will need to be redirected to another facility and the process of redirecting them. Furthermore, the affected party shall use its commercially reasonable efforts to resume proper performance within an appropriate period of time. Notwithstanding the foregoing, if the Force Majeure condition continues beyond thirty (30) days, the Parties shall jointly decide on an appropriate course of action that will permit fulfillment of the Parties’ objectives hereunder. The Contractor agrees that in the event of a delay or failure of performance by the Contractor, under the Contract due to a Force Majeure occurrence: a. The Commissioner may purchase from other sources (without recourse to and by the Contractor for the costs and expenses thereof) to replace all or part of the Products which are the subject of the delay, which purchases may be deducted from the Contract quantities without penalty or liability to the State, or b. The Contractor will make commercially reasonable efforts to provide Authorized Users with access to Products first in order to fulfill orders placed before the Force Majeure event occurred. The Commissioner agrees that Authorized Users shall accept allocated performance or deliveries during the occurrence of the Force Majeure event. Neither the Contractor nor the Commissioner shall be liable to the other for any delay in or failure of performance under the Contract due to a Force Majeure occurrence. Any such delay in or failure of performance shall not constitute default or give rise to any liability for damages. The existence of such causes of such delay or failure shall extend the period for performance to such extent as determined by the Contractor and the Commissioner to be necessary to enable complete performance by the Contractor if reasonable diligence is exercised after the cause of delay or failure has been removed. Notwithstanding the above, at the discretion of the Commissioner where the delay or failure will significantly impair the value of the Contract to the State or to Authorized Users, the Commissioner may terminate the Contract or the portion thereof which is subject to delays, and thereby discharge any unexecuted portion of the Contract or the relative part thereof. In addition, the Commissioner reserves the right, in his/her sole discretion, to make an equitable adjustment in the Contract terms and/or pricing should extreme and unforeseen volatility in the marketplace affect pricing or the availability of supply. "Extreme and unforeseen volatility in the marketplace" is defined as market circumstances which meet the following criteria: (i) the volatility is due to causes outside the control of Contractor; (ii) the volatility affects the marketplace or industry, not just the particular Contract source of supply; (iii) the effect on pricing or availability of supply is substantial; and (iv) the volatility so affects Contractor's performance that continued performance of the Contract would result in a substantial loss. Failure of the Contractor to agree to any adjustment shall be a dispute under the Disputes clause; provided however, that nothing in this clause shall excuse the Contractor from performing in accordance with the Contract as changed.

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