Remedial Action A. If a represented individual has worked more than one thousand fifty (1,050) hours in the twelve (12) month period from the individual’s original date of hire, the represented individual may request remedial action from the State Human Resources Director in accordance with WAC 357-49. Following the Director’s review of the remedial action request, an individual may file exceptions to the Director’s decision in accordance with WAC 357.
B. Remedial action is not subject to the provisions of the grievance procedure specified in Section 5.12, below.
Remedial Actions In the event of Recipient’s noncompliance with section 603 of the Act, other applicable laws, Treasury’s implementing regulations, guidance, or any reporting or other program requirements, Treasury may impose additional conditions on the receipt of a subsequent tranche of future award funds, if any, or take other available remedies as set forth in 2 C.F.R. § 200.339. In the case of a violation of section 603(c) of the Act regarding the use of funds, previous payments shall be subject to recoupment as provided in section 603(e) of the Act. Hatch Act. Recipient agrees to comply, as applicable, with requirements of the Hatch Act (5 False Statements. Recipient understands that making false statements or claims in connection with this award is a violation of federal law and may result in criminal, civil, or administrative sanctions, including fines, imprisonment, civil damages and penalties, debarment from participating in federal awards or contracts, and/or any other remedy available by law.
Environmental Remediation Failure to remediate (or pursue the remediation process with due diligence and good faith) within the time period required by law or governmental order, (or within a reasonable time in light of the nature of the problem if no specific time period is so established), environmental problems in violation of Applicable Law related to Properties of the Borrower and/or its Subsidiaries where the estimated cost of remediation is in the aggregate in excess of Seventy-Five Million Dollars ($75,000,000), in each case after all administrative hearings and appeals have been concluded.
Hazardous Materials; Remediation (a) If any material release or disposal of Hazardous Materials shall occur or shall have occurred on any real property or any other assets of any Borrower or any other Credit Party, such Credit Party will cause the prompt containment and removal of such Hazardous Materials and the remediation of such real property or other assets as is necessary to comply with all applicable Environmental Laws and Healthcare Laws and to preserve the value of such real property or other assets. Without limiting the generality of the foregoing, each Credit Party shall comply in all material respects with each Environmental Law and Healthcare Law requiring the performance at any real property by any Borrower or any other Credit Party of activities in response to the release or threatened release of a Hazardous Material.
(b) Credit Parties will provide Agent within thirty (30) days after written demand therefor with a bond, letter of credit or similar financial assurance evidencing to the reasonable satisfaction of Agent that sufficient funds are available to pay the cost of removing, treating and disposing of any Hazardous Materials or Hazardous Materials Contamination and discharging any assessment which may be established on any property as a result thereof, such demand to be made, if at all, upon Agent’s reasonable business determination that the failure to remove, treat or dispose of any Hazardous Materials or Hazardous Materials Contamination, or the failure to discharge any such assessment could reasonably be expected to have a Material Adverse Effect.
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>.