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.2.4. Developer shall retain each Noncompliance entry into the database until at least four years after the date of cure.
Notification Initiated by Developer. (a) 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 

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.

  • Electronic Fund Transfers Initiated By Third Parties You may authorize a third party to initiate electronic fund transfers between your account and the third party’s account. These transfers to make or receive payment may be one-time occurrences or may recur as directed by you. These transfers may use the Automated Clearing House (ACH) or other payments network. Your authorization to the third party to make these transfers can occur in a number of ways. For example, your authorization to convert a check or draft to an electronic fund transfer or to electronically pay a returned check or draft charge can occur when a merchant provides you with notice and you go forward with the transaction (typically, at the point of purchase, a merchant will post a sign and print the notice on a receipt). In all cases, these third party transfers will require you to provide the third party with your account number and credit union information. This information can be found on your check or draft as well as on a deposit or withdrawal slip. Thus, you should only provide your credit union and account information (whether over the phone, the Internet, or via some other method) to trusted third parties whom you have authorized to initiate these electronic fund transfers. Examples of these transfers include, but are not limited to: • Preauthorized credits. You may make arrangements for certain direct deposits to be accepted into your checking or savings account(s). • Preauthorized payments. You may make arrangements to pay certain recurring bills from your checking or savings account(s). • Electronic check or draft conversion. You may authorize a merchant or other payee to make a one-time electronic payment from your checking or share draft account using information from your check or draft to pay for purchases or pay bills. • Electronic returned check or draft charge. You may authorize a merchant or other payee to initiate an electronic funds transfer to collect a charge in the event a check or draft is returned for insufficient funds. Please also see Limitations on frequency of transfers section regarding limitations that apply to savings accounts. Direct Touch Banking Telephone Transfers - types of transfers - You may access your account by telephone 24 hours a day at (000) 000-0000 and Toll Free (866) 913- 3733 using your personal identification number, a touch tone phone, and Base account number, to: • transfer funds from checking to savings • transfer funds from savings to checking • transfer funds from savings to savings • make payments from checking to loan accounts with us • make payments from savings to loan accounts with us • get information about: - the account balance of checking accounts - the last five transactions to checking accounts - the account balance of savings accounts - the last five transactions to savings accounts Please also see Limitations on frequency of transfers section regarding limitations that apply to telephone transfers.

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

  • Procurement Related Complaints and Administrative Review 49.1 The procedures for making a Procurement-related Complaint are as specified in the TDS.

  • Search, Enquiry, Investigation, Examination And Verification a. The Property is sold on an “as is where is basis” subject to all the necessary inspection, search (including but not limited to the status of title), enquiry (including but not limited to the terms of consent to transfer and/or assignment and outstanding charges), investigation, examination and verification of which the Purchaser is already advised to conduct prior to the auction and which the Purchaser warrants to the Assignee has been conducted by the Purchaser’s independent legal advisors at the time of execution of the Memorandum.

  • CONTRACTOR’S RELATION TO THE STATE In the performance of this Agreement the Contractor is in all respects an independent contractor, and is neither an agent nor an employee of the State. Neither the Contractor nor any of its officers, employees, agents or members shall have authority to bind the State or receive any benefits, workers’ compensation or other emoluments provided by the State to its employees.

  • Obligation to Defend; Notice; Cooperation Whenever a claim arises for indemnification under this Section (the “Claim”), the relevant Indemnitee, as appropriate, will promptly notify the Indemnifying party and request the Indemnifying Party to defend the same. Failure to so notify the Indemnifying Party will not relieve the Indemnifying Party of any liability that the Indemnifying Party might have, except to the extent that such failure prejudices the Indemnifying Party's rights or ability to defend such Claim. The Indemnifying Party will have the right to defend against such Claim in which event the Indemnifying Party will give written notice to the Indemnitee of acceptance of the defense of such Claim and the identity of counsel selected by the Indemnifying Party. Except as set forth below, such notice to the relevant Indemnitee will give the Indemnifying Party full authority to defend, adjust, compromise, or settle such Claim with respect to which such notice has been given, except to the extent that any compromise or settlement might prejudice the Intellectual Property Rights or other rights of the relevant Indemnities. The Indemnifying Party will consult with the relevant Indemnitee prior to any compromise or settlement that would affect the Intellectual Property Rights or other rights of any Indemnitee, and the relevant Indemnitee will have the right to refuse such compromise or settlement and, at such Indemnitee’s sole cost, to take over defense of such Claim. Provided, however, that in such event the Indemnifying Party will not be responsible for, nor will it be obligated to indemnify the relevant Indemnitee against any damages, costs, expenses, or liabilities, including without limitation, attorneys’ fees, in excess of such refused compromise or settlement. With respect to any defense accepted by the Indemnifying Party, the relevant Indemnitee will be entitled to participate with the Indemnifying Party in such defense if the Claim requests equitable relief or other relief (other than monetary damages) that could affect the rights of the Indemnitee and also will be entitled to employ separate counsel for such defense at such Indemnitee's expense. In the event the Indemnifying Party does not accept the defense of any indemnified Claim as provided above, the relevant Indemnitee will have the right to employ counsel for such defense at the expense of the Indemnifying Party, and the Indemnifying Party shall be liable for all costs associated with Indemnitee’s defense of such Claim including court costs, and any settlement or damages awarded a third party. Each Party agrees to cooperate and to cause its employees and agents to cooperate with the other Party in the defense of any such Claim.

  • RIGHT TO DEVELOP AIRPORT It is covenanted and agreed that Authority reserves the right to further develop or improve the Airport and all landing areas and taxiways as it may see fit, regardless of the desires or views of Company or its subcontractors and without interference or hindrance.

Time is Money Join Law Insider Premium to draft better contracts faster.