Service Level Agreements If a Service or a Plan includes a Service Level Agreement (‘SLA’): (a) we are liable for any remedy or rebate allowed to you under the SLA; and (b) subject to clauses 34 to 38, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.
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.
Personnel Requirements and Documentation Grantee will; 1. maintain current personnel documentation on each employee. All documents must be factual and accurate. Health-related information must be stored separately with restricted access as appropriate under Tex. Gov. Code §552.102. Training records may be stored separately from the main personnel file but must be easily accessible upon request. Required documentation includes the following, as applicable: i. A copy of the current job description signed by the employee; ii. Application or resume with documentation of required qualifications and verification of required credentials; iii. Verification of work experience; iv. Annual performance evaluations; v. Personnel data that includes date hired, rate of pay, and documentation of all pay increases and bonuses; vi. Documentation of appropriate screening and/or background checks, to include probation or parole documentation; vii. Signed documentation of initial and other required training; and viii. Records of any disciplinary actions. 2. document authentication must include signature, credentials when applicable, and date. If the document relates to past activity, the date of the activity must also be recorded. Documentation must be permanent and legible. When it is necessary to correct a required document, the error must be marked through with a single line, dated, and initialed by the writer.
Disclosure to numbering service providers (a) Any Finance Party may disclose to any national or international numbering service provider appointed by that Finance Party to provide identification numbering services in respect of this Agreement, the Facility and/or one or more Obligors the following information: (i) names of Obligors; (ii) country of domicile of Obligors; (iii) place of incorporation of Obligors; (iv) date of this Agreement; (v) the names of the Agent and the Arranger; (vi) date of each amendment and restatement of this Agreement; (vii) amount of Total Commitments; (viii) currencies of the Facility; (ix) ranking of the Facility; (x) Termination Date for the Facility; (xi) changes to any of the information previously supplied pursuant to paragraphs (i) to (xi) above; and (xii) such other information agreed between such Finance Party and the Company, to enable such numbering service provider to provide its usual syndicated loan numbering identification services. (b) The Parties acknowledge and agree that each identification number assigned to this Agreement, the Facility and/or one or more Obligors by a numbering service provider and the information associated with each such number may be disclosed to users of its services in accordance with the standard terms and conditions of that numbering service provider. (c) Each Obligor represents that none of the information set out in paragraphs (i) to (xii) of paragraph (a) above is, nor will at any time be, unpublished price-sensitive information. (d) The Agent shall notify the Company and the other Finance Parties of: (i) the name of any numbering service provider appointed by the Agent in respect of this Agreement, the Facility and/or one or more Obligors; and (ii) the number or, as the case may be, numbers assigned to this Agreement, the Facility and/or one or more Obligors by such numbering service provider.
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).