Fault Incidents Clause Samples

The 'Fault Incidents' clause defines how situations involving errors, malfunctions, or failures in performance are identified and managed under the agreement. Typically, this clause outlines the process for reporting faults, the responsibilities of each party in addressing and rectifying the incident, and any timelines for resolution. For example, it may require the service provider to respond within a certain number of hours after being notified of a fault. The core function of this clause is to ensure that faults are handled promptly and transparently, minimizing disruption and clarifying accountability when issues arise.
Fault Incidents. 7.4.1 During the staffed hours of the NMC. When the NMC receives information on a fault incident it is logged. Where the fault is with the System, a fault response as per Section 7.3 is initiated. Where the fault incident is not with the System, but is within the responsibility of the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 When received, each fault incident shall be assessed and appointed a level of severity. In the event that the Client and the NMC / on-call engineer cannot agree which severity level should be allocated to the fault, the matter will be referred to each representative’s immediate superior for determination. During any disagreement, between the Client and the Service Provider, on the severity level to be appointed the more severe, higher level, will be used. 7.4.3 Outside the staffed hours of the NMC the scheduled on-call engineer will be alerted to all relevant alarms raised by the Service Provider's SCADA / automated alarm system. The relevant information will be communicated to the NMC the following morning for processing as per Section 7.3. 7.4.4 The following list describes the fault level categories.
View SourceView Similar (16)
Fault Incidents. 7.4.1 During the staffed hours of the NMC. When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 When received, each fault incident shall be assessed and appointed a level of severity. In the event that the Client, and/or any Authorised Representative nominated by the Client, and the NMC / on-call engineer cannot agree which severity level should be allocated to the fault, the matter will be referred to each representative’s immediate superior for determination. During any disagreement between the Client, and/or any Authorised Representative nominated by the Client, and the Service Provider on the severity level to be appointed the more severe, higher level, will be used. 7.4.3 Outside the staffed hours of the NMC the scheduled on-call engineer will be alerted to all relevant alarms raised by the Service Provider's SCADA / automated alarm system. The relevant information will be communicated to the NMC the following morning for processing as per Section 7.3. 7.4.4 The following list describes the fault level categories.
View SourceView Similar (8)
Fault Incidents. 7.4.1 During the staffed hours of the NMC. When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 When received, each fault incident shall be assessed and appointed a level of severity. In the event that the Client, and/or any Authorised Representative nominated by the Client, and the NMC / on-call engineer cannot agree which severity level should be allocated to the fault, the matter will be referred to each representative’s immediate superior for determination. During any disagreement between the Client, and/or any Authorised Representative nominated by the Client, and the Service Provider on the severity level to be appointed the more severe, higher level, will be used. 7.4.3 Outside the staffed hours of the NMC the scheduled on-call engineer will be alerted to all relevant alarms raised by the Service Provider's SCADA / automated alarm system. The relevant information will be communicated to the NMC the following morning for processing as per Section 7.3. 7.4.4 The following list describes the fault level categories. Level 1 >= Main Transmitter Site Faults 5. Total loss of, or a reduction in Power greater than Lower Failure Threshold in, the output of any main transmission site. 6. Total failure of the primary distribution system (Microwave Radio Links system) at the site or location. Level 2 >= Priority Relay or Priority Transposer Site Faults 5. Total loss of, or a reduction in Power greater than Lower Failure Threshold in, the output of any priority transposer or priority relay transmission site. 6. Total failure of the secondary distribution system (Rebroadcast) at a priority transposer site. Level 3 >= Transposer or Relay Site Faults 5. Total loss of, or a reduction in Power greater than Lower Failure Threshold in, the output of any transposer or relay transmission site. 6. Total failure of the secondary distribution system (Rebroadcast) at a transposer or re-transmitter site.
View SourceView Similar (8)
Fault Incidents. 7.4.1 When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 Subject to Clause 3 (Term), the Client may from time to time require the Service Provider to investigate documented generalised complaints concerning the Client’s coverage/signal strength in areas where adequate coverage is predicted by the Service Provider.
View Source
Fault Incidents. 7.4.1 When the NMC receives information on a fault incident it is logged. Where the fault is with the System a fault response is initiated by the NMC. Where the fault incident is not with the System, but is within the responsibility of the Client, and/or any Authorised Representative nominated by the Client, the NMC will contact the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 Subject to Clause 3 (Term), the Client may from time to time require the Service Provider to investigate documented generalised complaints concerning the Client’s coverage/signal strength in areas where adequate coverage is predicted by the Service Provider. 7.4.2.1 The Service Provider will be entitled to levy additional fees for such work, where such work is not covered by a pre-existing obligation under this Agreement and where the investigation proves that coverage/signal strength is as predicted. The Service Provider will conduct two investigations (maximum of three man days each) per Audio Stereo Pair(s)per year without levying additional fees. 7.4.2.2 The Service Provider will not be entitled to levy additional fees for such work, where such work is covered by a pre-existing obligation under this Agreement and where the investigation proves that coverage/signal strength is not as predicted. The Client may be entitled to a Service Credit under Section 11 in this situation.
View Source

Related to Fault Incidents

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Default in Performance (i) Any Loan Party shall fail to perform or observe any term, covenant, condition or agreement on its part to be performed or observed and contained in Section 8.4.(h) or Article IX.; or (ii) Any Loan Party shall fail to perform or observe any term, covenant, condition or agreement contained in this Agreement or any other Loan Document to which it is a party and not otherwise mentioned in this Section, and in the case of this subsection (b)(ii) only, such failure shall continue for a period of 30 days after the earlier of (x) the date upon which a Responsible Officer of the Borrower or such other Loan Party obtains knowledge of such failure or (y) the date upon which the Borrower has received written notice of such failure from the Administrative Agent.

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with Subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.