Software Error Reporting and Resolution Sample Clauses
Software Error Reporting and Resolution
Related to Software Error 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.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐▇▇▇▇▇▇-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Proposed Policies and Procedures Regarding New Online Content and Functionality By February 1, 2017, the Division will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the Division to provide equally effective alternative access. The Plan for New Content will require the Division, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternatives are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the Division online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the Division will officially adopt and fully implement the amended policies and procedures.
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.
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.