Notification Initiated by the Development Entity Sample Clauses

Notification Initiated by the Development Entity. (i) The Development Entity shall notify the Department in writing of the date of the occurrence of any Noncompliance Event as soon as reasonably practicable, and in any event within forty-eight (48) hours after the earlier of the time the Development Entity first obtains knowledge of or first should have reasonably known of the occurrence of the Noncompliance Event. The notice shall provide reasonable detail of the circumstances of the Noncompliance Event and shall identify the Noncompliance Event and Cure Period that is applicable to the relevant Noncompliance Event. (ii) The Development Entity shall notify the Department in writing of the occurrence of any Noncompliance Start Date and any Noncompliance Rectification Date (together with a detailed description of the manner in which the Noncompliance Event was cured and measures taken by the Development Entity to prevent the reoccurrence of the Noncompliance Event).
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Notification Initiated by the Development Entity. The Development Entity shall notify the Department in writing of the date of the occurrence of any Unavailability Event or Service Failure as soon as reasonably practicable, and in any event within forty-eight (48) hours after the earlier of the time the Development Entity first obtains knowledge of or first should have reasonably known of the occurrence of the Unavailability Event or Service Failure. The notice shall provide reasonable detail of the circumstances of the Unavailability Event or Service Failure.
Sample 1

Related to Notification Initiated by the Development Entity

  • initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.

  • 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).

  • Emergency Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-­‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.

  • TERMINATION BY THE CONTRACTOR If the Work is stopped for a period of thirty days under an order of any court or other public authority having jurisdiction, or as a result of an act of government, such as a declaration of a national emergency making materials unavailable, through no act or fault of the Contractor or a Subcontractor or their agents or employees or any other persons performing any of the Work under a contract with the Contractor, or if the Work should be stopped for a period of thirty days by the Contractor because the Architect has not issued a Certificate for Payment as provided in Paragraph 9.7 of these General Conditions or because the State has not made payment thereon as provided in Paragraph 9.7, then the Contractor may, upon seven additional days written notice to the State and the Architect, terminate the Contract and recover from the State payment for all Work executed and for any proven loss sustained upon any materials, equipment, tools, construction equipment and machinery, including reasonable profit and damages.

  • Review by the Association of Procurement Decisions The Procurement Plan shall set forth those contracts which shall be subject to the Association’s Prior Review. All other contracts shall be subject to Post Review by the Association.

  • Individual Negotiation This Agreement and each Transaction hereunder is subject to individual negotiation by the parties.

  • NOTIFICATION BY THE TRUST (a) The Trust agrees to advise NLD as soon as reasonably practical: (i) of any request by the SEC for amendments to the Registration Statement or any Prospectus then in effect; (ii) of the issuance by the SEC of any stop order suspending the effectiveness of the Registration Statement or any Prospectus then in effect or of the initiation of any proceeding for that purpose; (iii) of the happening of any event that makes untrue any statement of a material fact made in the Registration Statement or any Prospectus then in effect or which requires the making of a change in such Registration Statement or Prospectus in order to make the statements therein not misleading; (iv) of all actions of the SEC with respect to any amendment to any Registration Statement or any Prospectus which may from time to time be filed with the SEC; (v) if a current Prospectus is not on file with the SEC; and (vi) of all advertising, sales materials and other communications with the public required to be filed with FINRA. This obligation shall extend to all revisions of such communications. For purposes of this section, informal requests by or acts of the Staff of the SEC shall not be deemed actions of or requests by the SEC.

  • Release by the Contractor The acceptance by the Contractor of final payment shall release NYSERDA from all claims and liability that the Contractor, its representatives and assigns might otherwise have relating to this Agreement.

  • Review by the Bank of Procurement Decisions The Procurement Plan shall set forth those contracts which shall be subject to the Bank’s Prior Review. All other contracts shall be subject to Post Review by the Bank.

  • 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.

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