Corrective Action Plan Within fifteen (15) Business Days following the establishment of the Joint Remediation Committee, the Purchasers, in consultation with the Sellers, shall prepare and submit to the Joint Remediation Committee an initial draft of the Corrective Action Plan. The parties shall work in good faith through the Joint Remediation Committee to finalize the Corrective Action Plan within fifteen (15) Business Days of the Purchasers’ submission of the initial draft of the Correct Action Plan. At the end of such period, if the Sellers reasonably determine that the Corrective Action Plan proposed by the Purchasers (as may be modified over the course of such period) would not reasonably be expected to satisfactorily address the Major Default, then the Sellers may escalate the issue to the Head of Commercial Capital (or equivalent leader of any successor business unit) of the Seller Group and the Chief Executive Officer of the Bank Assets Purchaser (the “Senior Executives”) and the Senior Executives shall work collaboratively (including with the Joint Remediation Committee) to develop a mutually agreeable Corrective Action Plan within fifteen (15) Business Days.
Corrective Action Plans If the OAG finds deficiencies in ▇▇▇▇▇▇▇’s performance under this Grant Contract, the OAG, at its sole discretion, may impose one or more of the following remedies as part of a corrective action plan: increase of monitoring visits; require additional or more detailed financial and/or programmatic reports be submitted; require prior approval for expenditures; require additional technical or management assistance and/or make modifications in business practices; reduce the contract amount; and/or terminate this Grant Contract. The foregoing are not exclusive remedies, and the OAG may impose other requirements that the OAG determines will be in the best interest of the State.
Assistance in Litigation or Administrative Proceedings Business Associate shall make itself and any subcontractors, employees or agents assisting Business Associate in the performance of its obligations under this Agreement, available to County at no cost to County to testify as witnesses, or otherwise, in the event of litigation or administrative proceedings being commenced against County, its Directors, Managers or employees based upon claimed violation of HIPAA, the HIPAA regulations or other laws relating to security and privacy, which involves inactions or actions by the Business Associate, except where Business Associate or its subcontractor, employee or agent is a named adverse party.
Procurement Related Complaints and Administrative Review 49.1 The procedures for making a Procurement-related Complaint are as specified in the TDS. 49.2 A request for administrative review shall be made in the form provided under contract forms.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <▇▇▇▇▇://▇▇▇.▇▇▇-‐▇▇▇▇.▇▇▇/▇▇▇▇/▇▇▇▇/▇▇▇▇>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.