Outage Authority and Coordination Developer and Connecting Transmission Owner may each, in accordance with NYISO procedures and Good Utility Practice and in coordination with the other Party, remove from service any of its respective Attachment Facilities or System Upgrade Facilities and System Deliverability Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency State, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to schedule such removal on a date and time mutually acceptable to both the Developer and the Connecting Transmission Owner. In all circumstances either Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Party of such removal.
Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria
Name Collision Occurrence Management 6.1. No-‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements
Cloud Computing State Risk and Authorization Management Program In accordance with Senate Bill 475, Acts 2021, 87th Leg., R.S., pursuant to Texas Government Code, Section 2054.0593, Contractor acknowledges and agrees that, if providing cloud computing services for System Agency, Contractor must comply with the requirements of the state risk and authorization management program and that System Agency may not enter or renew a contract with Contractor to purchase cloud computing services for the agency that are subject to the state risk and authorization management program unless Contractor demonstrates compliance with program requirements. If providing cloud computing services for System Agency that are subject to the state risk and authorization management program, Contractor certifies it will maintain program compliance and certification throughout the term of the Contract.
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 <xxxx://xxxxxxxx.xxxxx.xxx/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) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>. 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 <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Administrative Civil Liability The Settling Respondent hereby agrees to the imposition of an administrative civil liability of $368,940 to resolve the alleged violation set forth in section II as follows: a. No later than 30 days after the Regional Water Board or its delegate signs this Stipulated Order, the Settling Respondent shall mail a check for State Water Resources Control Board Accounting Office Attn: ACL Payment P.O. Box 1888 Sacramento, CA 95812-1888 The Settling Respondent shall email a copy of the check to the State Water Board, Office of Enforcement (xxx.xxxxxx@xxxxxxxxxxx.xx.xxx), and to the Regional Water Board (xxxxx.xxxxx@xxxxxxxxxxx.xx.xxx). b. The Parties agree that the remaining $184,470 of the administrative liability shall be paid to the Regional Monitoring Program, care of the San Francisco Estuary Institute (SFEI), for implementation of a supplemental environmental project (SEP) named “High-Speed Mapping of Water Quality Parameters on the Eastern Shoal of South San Francisco Bay” as follows: i. $184,470 (SEP Amount) shall be paid in the manner described in section III, paragraph 1.b.ii, solely for use toward the SEP. Funding this project will result in high-speed mapping of water quality parameters covering the eastern shoals of South San Francisco Bay monthly over the course of four months. A complete description of the SEP is provided in Attachment B, incorporated herein by reference. ii. No later than 30 days after the Regional Water Board or its delegate signs this Stipulated Order, the Settling Respondent shall mail a check for $184,470, made payable to “Regional Monitoring Program,” referencing the Order number on page one of this Stipulated Order, to: Regional Monitoring Program c/o San Francisco Estuary Institute 0000 Xxxxxxx Xxxxxx Richmond, CA 94804 The Settling Respondent shall email a copy of the check to the State Water Board, Office of Enforcement (xxx.xxxxxx@xxxxxxxxxxx.xx.xxx), and to the Regional Water Board (xxxxx.xxxxx@xxxxxxxxxxx.xx.xxx).
Increasing Seat Belt Use in the United States E.O. 13043, amended by E.O. 13652, requires Recipients to encourage employees and contractors to enforce on-the-job seat belt policies and programs when operating company- owned, rented or personally-owned vehicle.
Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor
INVESTIGATIONS OF MISHAPS AND CLOSE CALLS In the case of a close call, mishap or mission failure, the Parties agree to provide assistance to each other in the conduct of any investigation. For all NASA mishaps or close calls, Partner agrees to comply with XXX 0000.0, "NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping".
