Error handling. The Customer shall report any errors without undue delay. The Contractor shall assist with identifying and rectifying errors within the framework defined in Appendix 2, and based on the framework set out in the service level agreement in Appendix 5. If the agreed deadlines are not complied with, the Customer may demand standardised compensation as stipulated in the service level agreement in Appendix 5. Unless otherwise is agreed in Appendix 5, the following error definitions shall apply: A Critical error - Error that results in the stoppage of the software or equipment, a loss of data, or in other functions that, based on an objective assessment, are of critical importance to the Customer not working as agreed. - The documentation being so incomplete or misleading that the Customer is unable to use the software or the equipment, or material parts thereof. B Serious error - Error that results in functions that, based on an objective assessment, are of importance to the Customer not working as described in the agreement, and which it is time-consuming and costly to work around. - The documentation being incomplete or misleading, and this resulting in the Customer being unable to use functions that, based on an objective assessment, are of importance to the Customer. C Less serious error - Error that results in individual functions not working as intended, but which can be worked around with relative ease by the Customer. - The documentation being incomplete or imprecise. To the extent that the services include the maintenance of standard software that the Contractor has not developed itself or does not maintain itself, or where elements of the services are in some other manner delivered by a third party and the Customer has not itself concluded a maintenance agreement with the software producer, the Contractor shall conclude the necessary agreement with the software producer. The terms and conditions for the maintenance that are agreed between the Contractor and the software producer shall be explicitly specified in a separate chapter in Appendix 2, and copies of the terms and conditions for the maintenance shall be appended as Appendix 10. If the Customer has itself concluded a maintenance agreement with the aforementioned software producer, these shall be appended to the Agreement as Appendix 10. The Contractor may request that the Customer assert or, with the agreement with the Customer, itself assert the Customer's rights in relation to the software pro...
Error handling. During the approval period the Customer shall, on an ongoing basis and without undue delay, report any errors to the Contractor in writing, which shall include a description of the errors, in accordance with the cooperation plan. The Contractor shall rectify the errors as quickly as possible. Errors shall be rectified in their order of priority. Unless otherwise agreed in Appendix 4, any errors shall be rectified, at the latest, by the end of the approval period. If errors or deviations occur during the approval period for the operational services and these prevent the Customer's examination of the operational services, the Customer shall have the right to extend the approval period by a period of time equal to the duration of the error or deviation.
Error handling a. Foodee acknowledges that errors are unpleasant, but also that the Client Experience is critical for service satisfaction. Foodee reserves the right to determine, within reason, an appropriate compensation for Errors in the Fulfillment Orders, and to pass along those costs to the Merchant.
b. Some specific errors & penalties are:
i. If Order Fulfillments are missed, significantly late, over 30% of items are missing, the Foodee reserves the right to waive all charges for the current order or provide for an immediate suitable replacement order, at the Merchant’s Cost, in addition to a no-charge order of a similar size within the next 30days.
ii. If less than 30% of Order items are missed on delivery, Merchant will provide delivery of missing items at no additional charge as soonest possible.
iii. If Merchants experience errors twice in a 30 day period, then Foodee reserves the right to cancel this agreement. Final payment will be net of any penalties.
c. Foodee acknowledges that errors of delivery may result of errors originating within the Foodee system. Error resolution from Foodee errors are at the sole cost of Foodee.
Error handling. Errors of concern to the TPA are grouped in the following categories: • Connectivity errors • Response errors • Sequencing errors • Business-specific errors Connectivity errors are detected as failure to receive the acknowledgment to the transmission of a message, such as the message that sends an action request to a server. Response errors are detected as failure to receive the results of an action. This subject is discussed in "Timing of Action Results". Sequencing errors are violations of the order of actions specified in the sequencing rules. See "Sequencing Rules". A sequencing error could be committed by a client (action invoker) or could result from a state error in the server. Therefore a sequencing error may require arbitration by the arbitrator specified in <TPAInfo>. See "Arbitration of TPA Disputes". NOTE: Sequencing errors can be handled by the framework and error-handling rules do not appear in the TPA. As part of processing sequencing errors, the framework can obtain the recent history of the conversation and send it to the arbitrator. Business-specific errors are included in payload of the message indicated by the <ResponseMessage> tag. NOTE: Other error conditions that may be indicated in the return code are system-related and can be trapped by the framework and handled by it. These conditions are not shown in the TPA and are defined in the application-programming documentation.
Error handling at any time failures of the surround- ing components (e.g. airbag activated, low energy in battery,
Error handling. 9.4.3.1 Perform [**] [**] [**] 9.4.3.2 [**] [**] [**]
Error handling. Errors and/or anomalies can occur during any data submission session. Actions to remedy potential error conditions for a Submission Session are identified below.
2.1-1: Error Handling
Error handling. The Customer (or if applicable, an Operating Company) or its representatives will provide all first level and second level support for Deliverables. Local Matters will provide third level technical support for all Deliverables only to Customer, any Operating Company as specified in an Order Form or their representatives; Local Matters will have no obligation to provide any support directly to Customer’s or Operating Companies’ customers or users. Technical support issues will be managed at the first and second level by the Customer, Operating Companies, or their third parties. First Level Support includes the following: · Clarification of functions and features of the Software; · Clarification of the Software documentation; · Guidance in using the Software; · Collection of relevant technical problem identification information, filter user/operator problems from real technical problems; and · Respond to customer with resolution or escalation information. Second Level Support includes the following: · Defect isolation and Software spec defect determination, and elimination of network, router, hardware and OS problems; · Assistance in identifying and verifying the causes of suspected Defects; · Advice on bypassing identified Defects, if reasonably possible; · Action plan definition; · Identification, localization and reporting of Defects that they are unable to resolve; · Respond to customer with resolution or escalation; · Restart Services / servers; and · Check Logs.
1. DE TELEFOONGIDS X.X. X.X. XXX 00000 0000 XX XXXXXXXXX XXX XXXXXXXXXXX
2. FONECTA OY X.X. XXX 000 XX-00000 XXXXXXXX FINLAND
3. XXXXXX BUSINESS DATA GMBH XXXXXXXXXXXXXX XXXXXXX 000 0000 XXXXXXX AUSTRIA
Error handling. This product must allow for different error handling Examples; • Entered information incorrectly message 1 is displayed • Incomplete information entry message 2 is displayed • Missing field information message 3 is displayed [SR4.10.1.2] ü Presentation layer requirement.
Error handling. 14.1 BT undertakes to correct all errors and omissions it observes or are drawn to its attention by third parties as soon as reasonably practicable. If the Customer observes or has brought to its attention any material errors or omissions which are found to be present in the BT Pathfinder System, then the Customer will use reasonable endeavours to notify BT of the errors in the manner agreed by the Parties. BT shall, with all reasonable assistance from the Customer, use all reasonable endeavours to verify such errors or omissions and include corrections thereof as soon as reasonably practicable.
14.2 If BT receives any complaint from a BT customer, another licensed telecommunications operator, or a competent authority which relates to or results from the Customer's use of the BT Pathfinder System or any information contained on it, upon BT's request, the Customer shall assist BT in its investigation of the complaint and take such steps as are reasonably necessary to remedy the complaint as soon as reasonably practicable.
