Fault Handling. (1) If the product fails, the Buyer shall cooperate with the Seller to obtain the faulty equipment usage information, including but not limited to: faulty equipment serial number, working temperature, usage mode, supporting energy storage inverter manufacturer/model/specification, power consumption equipment power information, PV system configuration information, fault phenomena, operating procedures, battery operation logs, etc.
(2) When both parties agree that the product belongs to the warranty scope, Buyer can use spare parts to replace the fault equipment, before using of spare parts to replace the fault equipment，the Buyer shall confirm with the Seller in writing and provide the serial number of the failure equipment and the serial number of the spare parts to be installed in time.
(3) After both parties have jointly agreed that the product belongs to the warranty scope, Buyer may replace the faulty components with the spare parts. Before replacing the faulty components with the spare parts, the Buyer shall confirm with the Seller in writing and provide the serial number of the failure equipment and the serial number of the spare parts to be installed in time.
(4) If the two parties disagree with whether the faulty equipment meets the warranty conditions, the products may be tested jointly by the ways approved by both parties, or the products shall be submitted to the third-party testing institutions recognized by both parties. Both parties can provide reasonable opinions on the test methods, basis and conclusions. The testing fee shall be borne by the Buyer first. If the testing result proves that the product meets the warranty conditions, the Seller shall pay the transportation fee and testing fee generated in full to the Buyer, and assume the responsibility for the faulty equipment warranty.
Fault Handling. 2.1 The Fault Contact Point of the Party to whom the fault is reported (“Reported Party”) shall immediately report the occurrence of such fault to the operation and maintenance in-charge of the Reported Party.
2.2 The Parties shall take immediate steps to rectify the problems. This includes but is not limited to arranging any replacement equipment or its parts thereof.
2.3 The Parties shall maintain the communication links at the affected site(s) and report on the progress of the restoration work.
2.4 The engineering teams deputed from both the sides shall try to rectify the fault to the best of their abilities and available resources.
2.5 The engineering teams shall keep their immediate supervisors informed about the progress.
2.6 Where a fault persists, and Party considers that progress of the remedy is not satisfactory such Party may require that the fault rectification be escalated to a higher level consisting of immediate supervisors of the Fault Contact Points.
2.7 Failure to rectify a fault within fifteen (15) Calendar Days after escalation in terms of Clause
Fault Handling. 11.1 The Customer shall report all Faults in the Service to the Company on the support telephone number or such other number as the Company may notify to the Customer from time to time.
11.2 The Company shall raise a trouble ticket and issue a Fault reference number to the Customer and shall repair the fault within 4 hours. If the Company fails to repair a Fault within the relevant timescale, the Customer may claim the compensation set out in Paragraphs 1.5, 1.6, 1.7, 1.8.
11.3 Timing starts when a trouble ticket is raised and a Fault reference number is issued to the Customer.
11.4 The Customer may obtain updates on the status of alarms and Faults by calling the support telephone number or such other number as the Company may notify to the Customer from time to time.
11.5 The Company shall notify the Customer by telephone or e-mail when the Fault has been repaired and the Service has been successfully restored. The trouble ticket will then be closed.
Fault Handling. During the fault investigation period by the Providing Operator, the Providing Operator may need to disconnect the Blockwiring circuits at the BIP or at the sub local box. The Providing Operator may also require assistance from the Requesting Operator in testing the faulty circuits. There may also be cases where the Providing Operator’s staff shall have to enter the customer premises to perform the fault investigation or restoration and if this is the case, the Providing Operator shall notify the Requesting Operator to arrange a joint visit. Upon clearing the fault, the Providing Operator shall provide the Requesting Operator the fault restoration time and action taken to restore the fault. The fault docket is then closed. The Providing Operator shall work towards the agreed target restoration time specified in Schedule 2 of the Blockwiring Agreement.
Fault Handling. In the event that Faircom dispatch a technician to the Subscriber to resolve a fault, a R250.00 (Two Hundred And Fifty Rand) call-out fee will be payable upfront. Should it later be determined by the technician that the fault was due to the malfunctioning of Faircom equipment or network elements, the call-out fee will be refunded to the Subscriber in full.
Fault Handling. Every player p maintains a player list Lp and adds to it in each round all players he reliably detects to be faulty. This list of detected players will never contain any correct player. Let p be a correct player. In order to nd conditions for the detection of faulty players by p, we rst derive a condition that must be satis ed for every internal node of the IG-tree corresponding to a correct player. Let r be an internal node corresponding to a correct player r. During information gathering, r distributes the same value treer( ) = v for his node to every player. Accordingly, in the following round, only a faulty player q may send to p a distinct value w = v for Finally, after n 3 + 1 runs, either all faulty players have been globally his node r. Hence there exists an adversary set A such that all players q with treep( rq) = v are covered by X. Xxxxxxxx, the set of already detected players Lp must be a subset of such an A, i.e. the condition : A ( c C( r) treep( rc) = v is satis ed. Hence player r can be reliably detected to be faulty by player p if there is no such value v. This rule can be applied during information gathering: player p adds player r to Lp if there is no such value v. By Lemma 2, this even holds for the converted values of r's child nodes. Hence we can apply the same rule for the resolved Fault detectio[nfdugring in9form:atiofn2gatherinjg (FD1): g[ player p for every internal node r: Lp := Lp
Fault Handling. 1.1 Definition of Fault and Unavailability Unscheduled Service unavailability shall be allowed up to 30 minutes per calendar month for each Service Item. Scheduled Service unavailability can occur in the following ways: The Supplier and/or any of its subcontractors if IUCC approved using subcontractor will from time to time have to carry out routine maintenance, upgrades or improvements to the network or network equipment. These works are defined as scheduled maintenance work, and can cause service outages. Schedule maintenance work will always be carried out during a pre-defined maintenance window, and will not be considered as unavailability. The Supplier's scheduled maintenance window for the Services will be on any day between 02.00 and 05.00 or as otherwise agreed between IUCC and the Supplier from time to time. The Supplier will inform the IUCC Network Operation Centre (NOC) at least three Business Days in advance by e-mail of any scheduled maintenance which might lead to service disruption (including the time, date, planned duration and description of the proposed work) except in case of emergency maintenance work on the Supplier's network. IUCC shall have the right to request the Supplier to postpone such scheduled maintenance for a reasonable period of time and if such scheduled maintenance is affecting only IUCC Service Items the Supplier shall accept such request. Emergency maintenance may be performed at any time, provided that the Supplier and the IUCC NOC have coordinated such maintenance. The total non-availability time for a Service Item due to scheduled maintenance work in any service quarter may not exceed 6 hours. Outages caused by any of the following are not considered as unavailability or faults: scheduled maintenance. Failure of IUCC’s equipment, power supply or environmental conditions; IUCC’s acts or omissions (or those of its employees, agents, representatives or sub-contractors); cabling or networks not included in the Services; and/or Force Majeure. Failure to enable the Supplier access to its equipment
Fault Handling. 2.4.1. The following steps are performed to increase the reliability of the Call Flow Analysis service:
2.4.2. Data transfers between CBT and OneLink will be accomplished using automated jobs directly to the external vendor's server.
2.4.3. If a data transfer fails [***]* .
2.4.4. [***]* . ------------------------------------- * Portions of this document indicated by [***] have been omitted and filed separately with the Commission.
2.4.5. [***]*
2.4.6. If the AIN network should fail for ANY REASON which directly impacts the performance of the AIN Call Flow Analysis Service, OneLink will be notified [***]* . [***]*
2.4.7. Failure notification will be followed with specification from CBT on how to manage any data impacting problems. Such problems include but are not limited to AIN platform failures, faulty network connections, database addressing problems, etc.
Fault Handling. 6.2.1 The fault handling service will be available 24 hours a day and 7 days a week including Public and Bank Holidays for Converged Ethernet Services (excluding any Wires Only Services which shall have the service outlined in Wires-Only Service section below).
6.2.2 All faults will be validated when reported and subsequently classified as:
6.2.2.1 Priority 1 - Total loss of service (hard down or no transmission in one or both directions);
6.2.2.2 Priority 2 – Service is available, but either reduced functionality or degradation is creating a significant business impact for the End User; and
6.2.2.3 Priority 3 - Service is available, but either reduced functionality or degradation is being experienced by the End User without any significant business impact for the End User.
Fault Handling. All fault handling shall be managed in accordance with the procedure as outlined in Section
3.1. All faults are shall be managed in accordance with the service levels detailed below.
