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.
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.
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.
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 6= v for his node r. Hence there exists an adversary set A 2 A and a unique value v such that all players q with treep( rq) 6= v are covered by A. Moreover, the set of already detected players Lp must be a subset of such an A, i.e. the condition 9v : 9A 2A : A (fc 2 C( r) j treep( rc) 6= vg[ Lp) 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 5 A player does not necessarily know which of the players he detected are globally detected and which are not. values as well and we obtain the following fault detection rules to be applied by player p for every internal node r: Fault detection during information gathering (FD1): p p p p L := L [ frg if 69v : :Q1(fc 2 C( r) j tree ( rc) 6= vg[ L ): Fault detection during data conversion (FD2): p p p p L := L [ frg if 69v : :Q1(fc 2 C( r) j resolve ( rc) 6= vg[ L ): Fault Masking: After a player r has been added to the list Lp by player p in some communication round k, then every message by player r in round k and any subsequent round is replaced by the default value 0. Once a player has been globally detected (by all correct players), he will be masked to send the same values to all correct players. Thus, every node r for which a value is received after player r's global detection will be common. We are ready to summarize the complete protocol (the description is given for the view by player p).
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 his node r. Hence there exists an adversary set A and a unique value v such that all players q with treep( rq) = v are covered by A. Moreover, the set of already detected players Lp must be a subset of such an A, i.e. the condition 9 92A f2 x x[
Fault Handling i. Any suspected faults should be reported to SCL Customer Services using the procedures detailed in the Service Handover Document to be provided on the Ready For Service Date.
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).
Fault Handling. 2.4.1. The following steps are performed to increase the reliability of the Call Flow Analysis service:
