Major Problem Sample Clauses

The "Major Problem" clause defines what constitutes a significant issue or defect within the context of a contract or agreement. Typically, this clause outlines specific criteria or thresholds that must be met for a problem to be considered "major," such as a defect that prevents the product or service from functioning as intended or causes substantial disruption. For example, in a software contract, a major problem might be a bug that causes system crashes or data loss. The core function of this clause is to clearly distinguish between minor and major issues, ensuring that both parties understand when heightened remedies or responses, such as repair, replacement, or even contract termination, may be triggered.
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.
View SourceView Similar (5)
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.
View Source
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.
View Source

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 ▇▇▇▇▇▇▇ or in their absence, the Local Union President, or Area ▇▇▇▇▇▇▇, or Chief ▇▇▇▇▇▇▇, 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 ▇▇▇▇▇▇▇, 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 ▇▇▇▇▇▇▇ or in their absence, the Local Union President, or Area ▇▇▇▇▇▇▇, or Chief ▇▇▇▇▇▇▇, 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 WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS 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 WCS 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 WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS 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 WCS’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 16.1 If a Force Majeure Event gives rise to a failure or delay in either party performing any obligation under this Agreement (other than any obligation to make a payment), that obligation will be suspended for the duration of the Force Majeure Event. 16.2 A party that becomes aware of a Force Majeure Event which gives rise to, or which is likely to give rise to, any failure or delay in that party performing any obligation under this Agreement, must: (a) promptly notify the other; and (b) inform the other of the period for which it is estimated that such failure or delay will continue. 16.3 A party whose performance of its obligations under this Agreement is affected by a Force Majeure Event must take reasonable steps to mitigate the effects of the Force Majeure Event.