Change Control All systems processing and/or storing PHI COUNTY discloses to 14 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 15 must have a documented change control procedure that ensures separation of duties and protects the 16 confidentiality, integrity and availability of data.
Change Control Procedure 34.1 In the event that either Party desires any change the terms of this Agreement or any Contract which may materially impact on the timings, scope, Specification or Charges of the Goods or Services, or the scope of either parties’ obligations under this Agreement or the relevant Contract, or which the relevant Party otherwise reasonably determines warrants the use of this change control procedure, the following procedures will apply:
(a) the Party requesting the change will deliver a “Change Request” (in the form (or substantially in the same form) contained in Schedule 5 to this Agreement) which describes:
(i) the nature of the change;
(ii) the reason for the change;
(iii) the effect that the requested change will have on the scope or Specification for the Goods or Services; and
(iv) any change to the Charges and the Term.
(b) Upon receipt of a Change Request, the receiving Party’s authorised representative will contact his/ her counterpart within 5 working days to discuss and agree the Change Request. The parties will negotiate the proposed changes to the Agreement and/or affected Contract in good faith and agree a timeline in which to finalise the Change Notice.
(c) Neither party is obliged to agree to a Change Request, but if the parties do agree to implement such a Change Request, the appropriate authorised representatives of both parties will sign the Change Request which will be effective from the date set out in the Change Request.
(d) If there is any conflict between the terms and conditions set out in the Agreement or any Contract and the Change Request, then the terms and conditions set out in the most recent fully executed Change Request will apply.
(e) The Supplier shall neither be relieved of its obligations to supply the Goods and/or Services in accordance with the terms and conditions of this Agreement or any Contract, nor be entitled to an increase in the Charges as the result of:
(i) a General Change in Law; or
(ii) a Specific Change in Law where the effect of that Specific Change in Law on the Goods and/or Services is reasonably foreseeable at the Commencement Date of this Agreement, or, where the Change Request relates to a Contract, the applicable Contract Commencement Date.
34.2 The Parties agree that any variations to the Agreement or any Contract to reflect non- material changes (including for example a change to the name/contact details of a Party’s representative) may be agreed in writing and shall not be required to be made in accordance with the procedure in this clause 34, provided always that UKRI shall, in their absolute discretion, decide whether a proposed change is non-material for these purposes.
Child Abuse Reporting Requirement Grantee will:
a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.
b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements.
c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency.
d. retain reporting documentation on site and make it available for inspection by the System Agency.
Progress Update Information included with the annual Data Access Request (DAR) renewal or Closeout summarizing the analysis of controlled-access datasets obtained through the DAR and any publications and presentations derived from the work.
Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.
Reporting Schedule Consultant shall report regularly, and not less frequent than once per week, to the Company his actions on behalf of the Company.
Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage.
Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users.
2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status.
2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:
1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have;
2. the names and positions of the members of the Compliance Committee required by Section III.A;
3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3;
4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1;
5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request);
6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request);
7. the following information regarding each type of training required by Section III.C:
a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions;
b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request.
8. a description of the Disclosure Program required by Section III.E;
9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group;
10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons;
11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims;
12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and
