Common use of Fault Incidents Clause in Contracts

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.

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

Fault Incidents. 7.4.1 7.5.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 Service Provider or the Client, the NMC will contact the Service Provider and / or the Client as soon as possible by email and/or telephone as per Section 7.3. 7.4.2 7.5.2 When received, each fault incident shall be assessed and appointed a level of severity. In the event that the Service Provider and / or 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 representative‟s immediate superior for determination. During any disagreement, between the Service Provider or the Client and the Service ProviderNetwork Operator, on the severity level to be appointed the more severe, higher level, will be used. 7.4.3 7.5.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 Network Operators 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 7.5.4 The following list describes the fault level categories.