Notification Initiated by Developer Sample Clauses

Notification Initiated by Developer. 11.2.1.1 Developer shall notify the Authority in writing of the date of the occurrence of any Noncompliance Event as soon as reasonably practicable, and in any event within forty-eight
AutoNDA by SimpleDocs
Notification Initiated by Developer. As an integral part of Developer’s self-monitoring obligations, Developer shall notify the Department in writing of the occurrence of any Noncompliance specified in Appendix 5, as it may be revised from time to time. Developer shall deliver such notice in writing as soon as reasonably practicable, and in any event within [seven] days, after Developer first obtains knowledge of or first should have reasonably known of the Noncompliance. The notice shall describe the Noncompliance in reasonable detail and shall identify the applicable cure period. Within [ten] days of receiving the notice, the Department shall deliver to Developer a written notice setting forth the Department’s determination whether the Noncompliance was cured during the cure period and, if not, whether to assess Noncompliance Points (a “notice of determination”).
Notification Initiated by Developer. ‌ 6.2.1.1 As an integral part of Developer’s self-monitoring obligations, Developer shall establish and maintain an electronic data base of each Noncompliance event specified in Section 4 of Division II, as it may be revised from time to time; and Developer shall enter each Noncompliance event into the data base in real time upon discovery. The format and design of the data base shall be subject to the Department’s reasonable approval. At a minimum, the data base shall (a) include a description of each Noncompliance in reasonable detail, (b) identify the Project location (if applicable), (c) identify the date and time of occurrence, (d) identify the applicable response time, if any, (e) indicate the applicable Cure Period, if any, as set forth in Section 4 of Division II, (f) indicate status, and (g) indicate date and time of cure. Developer shall assure that the Department has electronic access to the data base at all times and ability to make entries as provided in Sections 6.2.2 and 6.
Notification Initiated by Developer. ‌ 11.2.1.1 As an integral part of Developer’s self-monitoring obligations, Developer shall establish and maintain an electronic data base of each Noncompliance Event specified in Attachment 12-1 of Exhibit 12 to the Agreement, as it may be revised from time to time; and Developer shall enter each Noncompliance Event into the data base in real time upon discovery. The format and design of the data base shall be subject to IFA’s reasonable approval. At a minimum, the data base shall: a. Include a description of each Noncompliance Event in reasonable detail, including its assessment category as set forth in Attachment 12-1 of Exhibit 12 to the Agreement; b. Identify the East End Crossing location (if applicable); c. Identify the date and time of occurrence; d. Identify the applicable response time, if any; e. Indicate the applicable cure period, if any, as set forth in Attachment 12-1 of Exhibit 12 to the Agreement; f. Indicate status; and g. Indicate date and time of cure. 11.2.1.2 Developer shall ensure that IFA has electronic access to the data base at all times and ability to make entries as provided in Section 6.2.
Notification Initiated by Developer. Developer shall notify the Enterprises in writing of the occurrence of any Noncompliance Event or the commencement of any Non-Permitted Closure or Excused Closure as soon as reasonably practicable, and in any event within twenty-four (24) hours, after Developer first becomes aware that the Noncompliance Event has occurred or the Non-Permitted Closure or Excused Closure has commenced. Such notice shall:
Notification Initiated by Developer. ‌ 6.2.1.1 As an integral part of Developer’s self-monitoring obligations, Developer shall establish and maintain an electronic data base of each Noncompliance event specified in Section 4 of Division II, as it may be revised from time to time; and Developer shall enter each Noncompliance event into the data base in real time upon discovery. The format and design of the data base shall be subject to the Department’s reasonable approval. At a minimum, the data base shall (a) include a description of each Noncompliance in reasonable detail, (b) identify the Project location (if applicable), (c) identify the date and time of occurrence, (d) identify the applicable response time, if any, (e) indicate the applicable Cure

Related to Notification Initiated by Developer

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

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

  • Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.

  • Claims Initiated by Indemnitee To indemnify or advance expenses to Indemnitee with respect to an action, suit or proceeding (or part thereof) initiated by Indemnitee, except with respect to an action, suit or proceeding brought to establish or enforce a right to indemnification (which shall be governed by the provisions of Section 8(b) of this Agreement), unless such action, suit or proceeding (or part thereof) was authorized or consented to by the Board of Directors of the Corporation.

  • Initiation; Confirmation; Termination (a) An agreement to enter into a Transaction may be made orally or in writing at the initiation of either Buyer or Seller. On the Purchase Date for the Transaction, the Purchased Securities shall be transferred to Buyer or its agent against the transfer of the Purchase Price to an account of Seller. (b) Upon agreeing to enter into a Transaction hereunder, Buyer or Seller (or both), as shall be agreed, shall promptly deliver to the other party a written confirmation of each Transaction (a “Confirmation”). The Confirmation shall describe the Purchased Securities (including CUSIP number, if any), identify Buyer and Seller and set forth (i) the Purchase Date, (ii) the Purchase Price, (iii) the Repurchase Date, unless the Transaction is to be terminable on demand, (iv) the Pricing Rate or Repurchase Price applicable to the Transaction, and (v) any additional terms or conditions of the Transaction not inconsistent with this Agreement. The Confirmation, together with this Agreement, shall constitute conclusive evidence of the terms agreed between Buyer and Seller with respect to the Transaction to which the Confirmation relates, unless with respect to the Confirmation specific objection is made promptly after receipt thereof. In the event of any conflict between the terms of such Confirmation and this Agreement, this Agreement shall prevail. (c) In the case of Transactions terminable upon demand, such demand shall be made by Buyer or Seller, no later than such time as is customary in accordance with market practice, by telephone or otherwise on or prior to the business day on which such termination will be effective. On the date specified in such demand, or on the date fixed for termination in the case of Transactions having a fixed term, termination of the Transaction will be effected by transfer to Seller or its agent of the Purchased Securities and any Income in respect thereof received by Buyer (and not previously credited or transferred to, or applied to the obligations of, Seller pursuant to Paragraph 5 hereof) against the transfer of the Repurchase Price to an account of Buyer.

  • Notice of Litigation, Right to Prosecute, Etc No Fund shall be liable for indemnification under this Section 5.03 unless a Person shall have promptly notified such Fund in writing of the commencement of any litigation or proceeding brought against such Person in respect of which indemnity may be sought under this Section 5.03. With respect to claims in such litigation or proceedings for which indemnity by a Fund may be sought and subject to applicable law and the ruling of any court of competent jurisdiction, such Fund shall be entitled to participate in any such litigation or proceeding and, after written notice from such Fund to any Person, such Fund may assume the defense of such litigation or proceeding with counsel of its choice at its own expense in respect of that portion of the litigation for which such Fund may be subject to an indemnification obligation; provided however, a Person shall be entitled to participate in (but not control) at its own cost and expense, the defense of any such litigation or proceeding if such Fund has not acknowledged in writing its obligation to indemnify the Person with respect to such litigation or proceeding. If such Fund is not permitted to participate or control such litigation or proceeding under applicable law or by a ruling of a court of competent jurisdiction, such Person shall reasonably prosecute such litigation or proceeding. A Person shall not consent to the entry of any judgment or enter into any settlement in any such litigation or proceeding without providing each applicable Fund with adequate notice of any such settlement or judgment, and without each such Fund's prior written consent. All Persons shall submit written evidence to each applicable Fund with respect to any cost or expense for which they are seeking indemnification in such form and detail as such Fund may reasonably request.

  • Files Management and Record Retention relating to Grantee and Administration of this Agreement a. The Grantee shall maintain books, records, and documents in accordance with generally accepted accounting procedures and practices which sufficiently and properly reflect all expenditures of funds provided by Florida Housing under this Agreement. b. Contents of the Files: Grantee must maintain files containing documentation to verify all funds awarded to Grantee in connection with this Agreement, as well as reports, records, documents, papers, letters, computer files, or other material received, generated, maintained or filed by Grantee in connection with this Agreement. Grantee must also keep files, records, computer files, and reports that reflect any compensation it receives or will receive in connection with this Agreement.

  • Examination of work before covering up In respect of the work which the Authority’s Engineer is entitled to examine, inspect, measure and/or test before it is covered up or put out of view or any part of the work is placed thereon, the Contractor shall give notice to the Authority’s Engineer whenever any such work is ready and before it is covered up. The Authority’s Engineer shall then either carry out the examination, inspection or testing without unreasonable delay, or promptly give notice to the Contractor that the Authority’s Engineer does not require to do so. Provided, however, that if any work is of a continuous nature where it is not possible or prudent to keep it uncovered or incomplete, the Contractor shall notify the schedule of carrying out such work to give sufficient opportunity, not being less than 3 (three) business days’ notice, to the Authority’s Engineer to conduct its inspection, measurement or test while the work is continuing. Provided further that in the event the Contractor receives no response from the Authority’s Engineer within a period of 3 (three) business days from the date on which the Contractor’s notice hereunder is delivered to the Authority’s Engineer, the Contractor shall be entitled to assume that the Authority’s Engineer would not undertake the said inspection.

  • INSURANCE COMPANY NOT A PARTY TO THIS AGREEMENT The Insurer shall not be deemed a party to this Agreement, but will respect the rights of the parties as herein developed upon receiving an executed copy of this Agreement. Payment or other performance in accordance with the policy provisions shall fully discharge the Insurer from any and all liability.

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