Integration; Binding Effect; Survival of Termination This Agreement and the other Transaction Documents contain the final and complete integration of all prior expressions by the parties hereto with respect to the subject matter hereof and shall constitute the entire agreement among the parties hereto with respect to the subject matter hereof superseding all prior oral or written understandings. This Agreement shall be binding upon and inure to the benefit of the parties hereto and their respective successors and permitted assigns. This Agreement shall create and constitute the continuing obligations of the parties hereto in accordance with its terms and shall remain in full force and effect until the Final Payout Date; provided, however, that the provisions of Sections 5.01, 5.02, 5.03, 11.04, 11.06, 12.04, 13.01, 13.02, 14.04, 14.05, 14.06, 14.09, 14.11 and 14.13 shall survive any termination of this Agreement.
Reporting and Payment Procedures The Sub-recipient shall report at least quarterly all expenses incurred and associated project activities carried out with CDBG and non-CDBG funds. The Sub-recipient shall follow the reimbursement request process as set forth by the County and CDBG program administrator. Reimbursements are subject to the following but not limited to: eligibility of expenses, proper reporting and expense documentation, availability of funds, and authorization by the County and CDBG program administrator. DocuSign Envelope ID: E4D55B2A-BBB1-48FF-A259-0798F37C0F0E
Billing and Payment Procedure for Forest Products Delivered The State will compute and forward to Purchaser a billing statement of charges for forest products delivered during the billing period at the delivered rate shown in P- 028.2 clause. After receipt of the billing statement, Purchaser’s payment must be received by the Department of Natural Resources on or before the due date shown on the billing statement. Purchaser agrees to make payment, payable to the Department of Natural Resources. Failure to pay on time for forest products delivered is considered a breach of contract. Included with the billing statement will be a summary report for the billing period compiled by the State or their log and load reporting service. The State will adjust final xxxxxxxx to account for any State approved payment reductions. Advance payments made under P-045 or P-045.2 remaining on account above the value for the charges shall be returned to Purchaser within 30 days following the final report of charges. Refunds not made within the 30 day period will accrue interest at the interest rate, as established by WAC 000-000-000, computed on a daily basis until paid.
Integration; Binding Effect; Survival of Terms (a) This Agreement and each other Transaction Document contain the final and complete integration of all prior expressions by the parties hereto with respect to the subject matter hereof and shall constitute the entire agreement among the parties hereto with respect to the subject matter hereof superseding all prior oral or written understandings.
(b) This Agreement shall be binding upon and inure to the benefit of the parties hereto and their respective successors and permitted assigns (including any trustee in bankruptcy). This Agreement shall create and constitute the continuing obligations of the parties hereto in accordance with its terms and shall remain in full force and effect until terminated in accordance with its terms; provided, however, that the rights and remedies with respect to (i) any breach of any representation and warranty made by any Seller Party pursuant to Article V, (ii) the indemnification and payment provisions of Article X, and Sections 14.5 and 14.6 shall be continuing and shall survive any termination of this Agreement.
PROCEDURE FOR NOTIFICATION AND APPLICATION FOR INDEMNIFICATION (a) Indemnitee agrees to notify promptly the Company in writing upon being served with any summons, citation, subpoena, complaint, indictment, information or other document relating to any Proceeding, claim, issue or matter therein which may be subject to indemnification, hold harmless or exoneration rights, or advancement of Expenses covered hereunder. The failure of Indemnitee to so notify the Company shall not relieve the Company of any obligation which it may have to Indemnitee under this Agreement, or otherwise.
(b) Indemnitee may deliver to the Company a written application to indemnify, hold harmless or exonerate Indemnitee in accordance with this Agreement. Such application(s) may be delivered from time to time and at such time(s) as Indemnitee deems appropriate in his or her sole discretion. Following such a written application for indemnification by Indemnitee, Indemnitee’s entitlement to indemnification shall be determined according to Section 12(a) of this Agreement.
Dispute Resolution Mandatory Arbitration Class Action Waiver SAMPLE
(a) Claims Subject to Arbitration. Except as expressly provided below, the parties agree that to the fullest extent permitted by applicable law, any dispute arising out of or relating in any way to this Agreement or a similar prior agreement, the Property or the relationship between Resident and Owner or Manager (including matters occurring prior to the date of this Agreement and disputes also involving third parties) (collectively, “Claims”) will, at the election of either party, be resolved by arbitration, including any dispute about arbitrability, such as scope and enforceability.
Alternative Dispute Resolution Limitations This is a requirement of the TIPS Contract and is non-negotiable. No Waiver of TIPS Immunity This is a requirement of the TIPS Contract and is non-negotiable. 5 5 Payment Terms and Funding Out Clause This is a requirement of the TIPS Contract and is non-negotiable. 6
Indemnification Procedure for Third Party Claims (a) In the event that any party (the “Indemnified Person”) desires to make a claim against any other party (the “Indemnifying Person”) in connection with any Losses for which the Indemnified Person may seek indemnification hereunder in respect of a claim or demand made by any Person not a party to this Agreement against the Indemnified Person (a “Third-Party Claim”), such Indemnified Person must notify the Indemnifying Person in writing, of the Third-Party Claim (a “Third-Party Claim Notice”) as promptly as reasonably possible after receipt, but in no event later than fifteen (15) calendar days after receipt, by such Indemnified Person of notice of the Third-Party Claim; provided, that failure to give a Third-Party Claim Notice on a timely basis shall not affect the indemnification provided hereunder except to the extent the Indemnifying Person shall have been actually and materially prejudiced as a result of such failure. Upon receipt of the Third-Party Claim Notice from the Indemnified Person, the Indemnifying Person shall be entitled, at the Indemnifying Person’s election, to assume or participate in the defense of any Third-Party Claim at the cost of Indemnifying Person. In any case in which the Indemnifying Person assumes the defense of the Third-Party Claim, the Indemnifying Person shall give the Indemnified Person ten (10) calendar days’ notice prior to executing any settlement agreement and the Indemnified Person shall have the right to approve or reject the settlement and related expenses; provided, however, that upon rejection of any settlement and related expenses, the Indemnified Person shall assume control of the defense of such Third-Party Claim and the liability of the Indemnifying Person with respect to such Third-Party Claim shall be limited to the amount or the monetary equivalent of the rejected settlement and related expenses.
(b) The Indemnified Person shall retain the right to employ its own counsel and to discuss matters with the Indemnifying Person related to the defense of any Third-Party Claim, the defense of which has been assumed by the Indemnifying Person pursuant to Section 10.3(a) of this Agreement, but the Indemnified Person shall bear and shall be solely responsible for its own costs and expenses in connection with such participation; provided, however, that, subject to Section 10.3(a) above, all decisions of the Indemnifying Person shall be final and the Indemnified Person shall cooperate with the Indemnifying Person in all respects in the defense of the Third-Party Claim, including refraining from taking any position adverse to the Indemnifying Person.
(c) If the Indemnifying Person fails to give notice of the assumption of the defense of any Third-Party Claim within a reasonable time period not to exceed forty-five (45) days after receipt of the Third-Party Claim Notice from the Indemnified Person, the Indemnifying Person shall no longer be entitled to assume (but shall continue to be entitled to participate in) such defense. The Indemnified Person may, at its option, continue to defend such Third-Party Claim and, in such event, the Indemnifying Person shall indemnify the Indemnified Person for all reasonable fees and expenses in connection therewith (provided it is a Third-Party Claim for which the Indemnifying Person is otherwise obligated to provide indemnification hereunder). The Indemnifying Person shall be entitled to participate at its own expense and with its own counsel in the defense of any Third-Party Claim the defense of which it does not assume. Prior to effectuating any settlement of such Third-Party Claim, the Indemnified Person shall furnish the Indemnifying Person with written notice of any proposed settlement in sufficient time to allow the Indemnifying Person to act thereon. Within fifteen (15) days after the giving of such notice, the Indemnified Person shall be permitted to effect such settlement unless the Indemnifying Person (a) reimburses the Indemnified Person in accordance with the terms of this Article 10 for all reasonable fees and expenses incurred by the Indemnified Person in connection with such Claim; (b) assumes the defense of such Third-Party Claim; and (c) takes such other actions as the Indemnified Person may reasonably request as assurance of the Indemnifying Person’s ability to fulfill its obligations under this Article 10 in connection with such Third-Party Claim.
Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.
Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.
