Problems reporting and resolution Sample Clauses

Problems reporting and resolution. Reporting of problems may be via telephone, fax, e-mail, postal service or any other agreed means. The Contractor shall establish the severity of a reported Hardware and/or Operating System (including other related software e.g. network management system) problem jointly with the Client according to the following definitions- i. catastrophic problem - system is down, user is unable to function or complete work. This includes a non- isolated, consistently reproducible problem resulting in system crash. ii. major problem - this covers problems which must be corrected but do not prevent progress from being made, and/or problems which do not require immediate attention and includes- I. isolated, consistently reproducible problem resulting in a system crash; II. failure of a significant function of the equipment. iii. minor problem - a problem which does not have a major impact on operation or development, or for which an adequate workaround exists, and includes requests for add-ons. iv. non-reproducible error - a reported error which Contractor cannot diagnose or reproduce. The Contractor shall report back to the Client within two hours of him being notified by the Client of a problem. The Contractor shall inform the Client in his report of the severity level assigned to the problem. Based on the severity level of the problem, the Contractor shall provide the Client with either - - a solution, - a workaround, - a report stating that further research is required, or - a report stating that the problem cannot be reproduced, and will not be fixed. The Contractor may re-classify the problem after consultation with the Client as more information becomes available. After the assessment of the severity level of the problem, the COMPUTER SYSTEM (or replacement equipment whose configuration should be at least as per Schedule I) should be up and running within the time frame given below: Catastrophic Within 6 working hours Major Within 12 working hours Minor Within 24 working hours Non- reproducible Within 72 working hours The contractor will have to provide the client with a report stating that the problem cannot be reproduced and will not be fixed. The Contractor shall keep the Client informed of the problem report resolution progress by phone, fax, or e-mail.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Problems reporting and resolution

  • COMPLAINTS HANDLING AND RESOLUTION 44.1 The Supplier shall notify the Authority of any Complaints made by Other Contracting Bodies, which are not resolved by operation of the Supplier's usual complaints handling procedure within five (5) Working Days of becoming aware of that Complaint and such notice shall contain full details of the Supplier's plans to resolve such Complaint. 44.2 Without prejudice to any rights and remedies that a complainant may have at Law, including under this Framework Agreement or a Call-Off Contract, and without prejudice to any obligation of the Supplier to take remedial action under the provisions of this Framework Agreement or a Call-Off Contract, the Supplier shall use its best endeavours to resolve the Complaint within ten (10) Working Days and in so doing, shall deal with the Complaint fully, expeditiously and fairly. 44.3 Within two (2) Working Days of a request by the Authority, the Supplier shall provide full details of a Complaint to the Authority, including details of steps taken to achieve its resolution.

  • Problem Resolution The parties shall meet and attempt to resolve all disputes and differences that may arise between the parties hereto concerning construction, interpretation, performance, operations, or breach of the matters referred to in this Agreement prior to seeking any legal remedy.

  • DNS resolution RTT Refers to either “UDP DNS resolution RTT” or “TCP DNS resolution RTT”.

  • TCP DNS resolution RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the DNS response for only one DNS query. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

  • UDP DNS resolution RTT Refers to the RTT of the sequence of two packets, the UDP DNS query and the corresponding UDP DNS response. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

  • PERFORMANCE MONITORING AND REPORTING Performance indicators

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Safeguards Monitoring and Reporting The Borrower shall do the following or cause the Project Executing Agency to do the following:

  • Informal Resolution Outcomes a. When a complainant approaches an administrative officer and alleges harassment by another BCTF member, the following shall apply: i. All discussions shall be solely an attempt to mediate the complaint; ii. Any and all discussions shall be completely off the record and will not form part of any record; iii. Only the complainant, respondent, and administrative officer shall be present at such meetings iv. No discipline of any kind would be imposed on the respondent; and v. The BCTF and its locals, based on the foregoing, will not invoke the notice of investigation and other discipline provisions of the collective agreement at meetings pursuant to Article E.2.5.a. b. Should a resolution be reached between the complainant and the respondent at Step One under the circumstances of Article E.2.5.a, it shall be written up and signed by both. Only the complainant and the respondent shall have copies of the resolution and they shall be used only for the purpose of establishing that a resolution was reached. No other copies of the resolution shall be made. c. In the circumstances where a respondent has acknowledged responsibility pursuant to Article E.

  • DNSSEC proper resolution There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!