Heightened Alert State Sample Clauses

Heightened Alert State. An exhaustive list of conditions used to evaluate the decision to trigger a heightened alert is not detailed in this high-level description. Examples of conditions sufficient to invoke a state of heightened alert might include a registry operator requesting a transition to EBERO or the ICANN risk assessment specialists concluding that there is a substantial risk and credible threat that the registry operator would—within 48 hours—fail to meet its obligations under its registry agreement. During any Heightened Alert State, ICANN will attempt to work with the registry operator to remediate the underlying problem(s). Uncured Compliance notice of (a) failure to receive notification of required escrow deposits; or (b) failure of deposits to pass verification, for a period of 6 or more days.
AutoNDA by SimpleDocs
Heightened Alert State. ‌ An exhaustive list of conditions used to evaluate the decision to trigger EBERO is not detailed in this high-level description. Example of conditions sufficient to invoke a state of heightened alert might include a registry requesting a transition to EBERO or a registry reaching a failure state that has utilized 10% of the emergency threshold timing window as described in Specification 10 of the new gTLD agreement. During a Heightened Alert State, ICANN will be trying to work with the registry to remediate the service problems. 1008 minutes after the issuance of a Compliance notice of (a) failure to receive notification of required escrow deposits; or (b) failure of deposits to pass verification.

Related to Heightened Alert State

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting

  • Customer Identification Program Notice To help the U.S. government fight the funding of terrorism and money laundering activities, U.S. Federal law requires each financial institution to obtain, verify, and record certain information that identifies each person who initially opens an account with that financial institution on or after October 1, 2003. Certain of PNC’s affiliates are financial institutions, and PNC may, as a matter of policy, request (or may have already requested) the Fund’s name, address and taxpayer identification number or other government-issued identification number, and, if such party is a natural person, that party’s date of birth. PNC may also ask (and may have already asked) for additional identifying information, and PNC may take steps (and may have already taken steps) to verify the authenticity and accuracy of these data elements.

  • WASHINGTON’S STATEWIDE PAYEE DESK Contractor represents and warrants that Contractor is registered with Washington’s Statewide Payee Desk, which registration is a condition to payment.

  • APARTMENT OWNERSHIP ACT (OF THE RELEVANT STATE The Promoter has assured the Allottees that the project in its entirety is in accordance with the provisions of the [Please insert the name of the state Apartment Ownership] Act). The Promoter showing compliance of various laws/regulations as applicable in .

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Lightyear’s data from BellSouth’s data, the following shall apply: (1) Lightyear will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Lightyear’s End User accounts which are resident in LIDB pursuant to this Agreement. Lightyear authorizes BellSouth to place such charges on Lightyear’s xxxx from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls. (2) Charges for such services shall appear on a separate BellSouth xxxx xxxx identified with the name of the B&C Customers for which BellSouth is billing the charge. (3) Lightyear shall have the responsibility to render a billing statement to its End Users for these charges, but Lightyear shall pay BellSouth for the charges billed regardless of whether Lightyear collects from Lightyear’s End Users. (4) BellSouth shall have no obligation to become involved in any disputes between Lightyear and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Lightyear. It shall be the responsibility of Lightyear and the B&C Customers to negotiate and arrange for any appropriate adjustments.

  • Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • Normal Commercial Relations Anything contained in this Indenture to the contrary notwithstanding, the Loan Trustee, any Noteholder or any other party to any of the Operative Documents or the Pass Through Documents or any of their affiliates may conduct any banking or other financial transactions, and have banking or other commercial relationships, with the Company, fully to the same extent as if this Indenture were not in effect, including without limitation the making of loans or other extensions of credit to the Company for any purpose whatsoever, whether related to any of the transactions contemplated hereby or otherwise.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the Funder has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Interconnection Customer Authority Consistent with Good Utility Practice, this LGIA, and the CAISO Tariff, the Interconnection Customer may take actions or inactions with regard to the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities during an Emergency Condition in order to (i) preserve public health and safety, (ii) preserve the reliability of the Large Generating Facility or the Interconnection Customer’s Interconnection Facilities,

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!