Error handling Sample Clauses

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: Level Category Description 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 r...
AutoNDA by SimpleDocs
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.
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. 9.4.3.1 Perform [**] [**] [**] 9.4.3.2 [**] [**] [**]
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. [ ] = CERTAIN CONFIDENTIAL INFORMATION CONTAINED IN THIS DOCUMENT, MARKED BY BRACKETS, IS FILED WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO RULE 406 OF THE SECURITIES EXCHANGE ACT OF 1933, AS AMENDED. SCHEDULE 3 OPERATING COMPANIES
Error handling. 6.1 If the Operator is made aware of any material errors or omissions in the Licensed Database the Operator shall notify BT without delay of the errors, at the following address: The Operator Services Information Systems Manager BT Operator Services 3rd Xxxxx Xxxxx Xxxxxxxx Xxxxxx Xxxxxxxx Xxxx XXXXX XX00 0XX or to such other address as BT may notify to the Operator.
Error handling. This section describes the error handling roles and responsibilities for established EDI Trading Partners, as well as systems and processes for error correction. APMT – Horizon Lines 7 • EDI Format Errors – Errors with EDI Standards, syntax, translation EDI format errors are those that prevent the EDI message and data from being processed through the EDI Translation Application. This includes errors that do not adhere to EDI Standards, syntax issues and translation issues. When an EDI message has errors in format or segment data requirements, the message suspends in the translation process. We will indicate the error back to the partner within the 997. The partner should look into the process further to determine why the message error in the first place. Our translator checks all outbound messages to our partners for syntax related issues prior to transmission.
AutoNDA by SimpleDocs
Error handling. This section describes the error handling roles and responsibilities for established EDI Trading Partners, as well as systems and processes for error correction. APMT – Horizon Lines 7
Error handling. Error transaction[s] received by the system along with the details
Error handling. 67. 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.
Time is Money Join Law Insider Premium to draft better contracts faster.