The Performance Improvement Process (a) The Performance Improvement Process will focus on the risks of non- performance and problem-solving. It may include one or more of the following actions: (1) a requirement that the HSP develop and implement an improvement plan that is acceptable to the LHIN; (2) the conduct of a Review; (3) a revision and amendment of the HSP’s obligations; and (4) an in-year, or year end, adjustment to the Funding, among other possible means of responding to the Performance Factor or improving performance. (b) Any performance improvement process begun under a prior service accountability agreement that was not completed under the prior agreement will continue under this Agreement. Any performance improvement required by a LHIN under a prior service accountability agreement will be deemed to be a requirement of this Agreement until fulfilled or waived by the LHIN.
Payment Process Subject to the terms and conditions established by the Agreement, the pricing per deliverable established by the Grant Work Plan, and the billing procedures established by Department, Department agrees to pay Grantee for services rendered in accordance with Section 215.422, Florida Statutes (F.S.).
Document Imaging Investor shall be entitled, in its sole discretion, to image or make copies of all or any selection of the agreements, instruments, documents, and items and records governing, arising from or relating to any of Company’s loans, including, without limitation, this Agreement and the other Transaction Documents, and Investor may destroy or archive the paper originals. The parties hereto (i) waive any right to insist or require that Investor produce paper originals, (ii) agree that such images shall be accorded the same force and effect as the paper originals, (iii) agree that Investor is entitled to use such images in lieu of destroyed or archived originals for any purpose, including as admissible evidence in any demand, presentment or other proceedings, and (iv) further agree that any executed facsimile (faxed), scanned, emailed, or other imaged copy of this Agreement or any other Transaction Document shall be deemed to be of the same force and effect as the original manually executed document.
Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).
Appeals Process The Participants acknowledge that, pursuant to local ordinances, regulations, and rules, each Participant has its own procedures by which matters relating to the calculation, assessment, and collection of business license taxes may be appealed. With respect to Impositions subject to this Agreement, however, each Participant has enacted a local ordinance by which appeals relating to such Impositions are excluded from the otherwise applicable local ordinance. Each Participant agrees that the appeals process described in this Section shall apply to all appeals relating to Impositions subject to this Agreement. Each Participant hereby consents to the adoption of the appeals process described in this Section; specifically declares its intention that such appeals process shall be deemed an exception to its otherwise applicable local ordinances, regulations, and rules; and agrees that it has or will approve such appeals process by appropriate local action. (a) There is hereby created a board for purposes of hearing appeals pursuant to this Section (the “Appeals Board”). The Appeals Board shall contain three members. The President of the Association, the Executive Director of the Association, and the President of the South Carolina Business Licensing Officials Association (“BLOA”) shall each serve ex officio as members of the Appeals Board, with terms of office coterminous with their terms as officers of the Association or BLOA, as appropriate. The President of the Association, or in his or her absence the Executive Director of the Association, shall serve as chair at meetings of the Appeals Board. (b) With respect to the calculation, assessment, and collection of Impositions, the following appeals process, as required by Section 6-1-410, shall apply. (1) If a taxpayer fails or refuses to pay an Imposition by the date on which such Imposition is due, the LRS Business License Official may serve notice of assessment of the Imposition due on the taxpayer by mail or personal service. Within thirty days after the date of postmark or personal service, a taxpayer may request, in writing with reasons stated, an adjustment of the assessment. An informal conference between the LRS Business License Official and the taxpayer must be held within fifteen days of the receipt of the request, at which time the taxpayer may present any information or documents in support of the requested adjustment. Within five days after the conference, the LRS Business License Official shall issue a notice of final assessment and serve the taxpayer by mail or personal service with the notice and provide a form for any further appeal of the assessment by the taxpayer. (2) Within thirty days after the date of postmark or personal service, the taxpayer may appeal the notice of final assessment by filing a completed appeal form with the LRS Business License Official, by mail or personal service, and by paying to LRS in protest at least eighty percent of the business license tax based on the final assessment. The appeal must be heard and determined by the Appeals Board. The Appeals Board shall provide the taxpayer with written notice of the hearing and with any rules of evidence or procedure prescribed by the Appeals Board. The hearing must be held within thirty days after receipt of the appeal form unless continued to another date by agreement of the parties. A hearing by the Appeals Board must be held at a regular or specially called meeting of the Appeals Board. At the appeals hearing, the taxpayer and LRS have the right to be represented by counsel, to present testimony and evidence, and to cross-examine witnesses. The hearing must be recorded and must be transcribed at the expense of the party so requesting. The Appeals Board shall decide the assessment by majority vote. The Appeals Board shall issue a written decision explaining the basis for the decision with findings of fact and conclusions and shall inform the taxpayer of the right to request a contested case hearing before the Administrative Law Court. The written decision must be filed with the LRS Business License Official and served on the taxpayer by mail or personal service. The decision is the final decision of LRS on the assessment. (3) Within thirty days after the date of postmark or personal service of LRS’s written decision on the assessment, a taxpayer may appeal the decision to the Administrative Law Court in accordance with the rules of the Administrative Law Court.
Claims Processing BCBSM will process Provider's Clean Claims submitted in accordance with this Agreement in a timely fashion.
Review Process A/E's Work Product will be reviewed by County under its applicable technical requirements and procedures, as follows:
Claims Process We intend to appoint the senior trustee as the authorized representative to take action on behalf of holders of each series of the notes under the guarantee. The authorized representative will agree to make a demand of the FDIC upon our failure to pay interest or principal on any series of the notes when due. As provided in the FDIC’s regulations, a holder will also have the option to elect not to be represented by the authorized representative. Upon our failure to pay interest or principal, the authorized representative and a holder that has elected not to be so represented must follow the FDIC’s required procedures for making a demand under the guarantee. In addition to the procedures described below, the authorized representative will be required when making a demand, to the extent not previously provided in the master agreement, to provide the FDIC with information regarding its authority, including: its financial and organizational capacity to act as representative, its exclusive authority to act on behalf of each noteholder and its fiduciary responsibility to the noteholders when acting as such, as established by the senior indenture, and its authority to make the assignment of each noteholder’s right, title, and interest in the notes to the FDIC. Any demand under the guarantee must be accompanied by a proof of claim, satisfactory in form and content to the FDIC, which includes evidence of the occurrence of a payment default and the claimant’s ownership of the applicable notes. The claimant must provide to the FDIC an assignment, satisfactory in form and content to the FDIC, of the noteholder’s right, title and interest in the notes to the FDIC and the transfer to the FDIC of any claim in any insolvency proceeding against us. The assignment must also grant to the FDIC the right to receive any and all distributions on the note from the proceeds of any bankruptcy. If a holder receives a payment on a note from a bankruptcy, any obligation of the FDIC under the guarantee would be reduced proportionally. Demands must be made by the authorized representative or by a holder that elects not to be represented by the authorized representative within 60 days of the occurrence of the payment default. Upon payment by the FDIC of any amount under the guarantee, the FDIC will be subrogated to the rights of the recipient noteholder against us, including in respect of any insolvency proceeding, to the extent of such payment.
Construction of this Amendment; Participation Agreement (a) This Amendment shall be interpreted to be consistent with, and to facilitate compliance with and reliance on, Rule 30e-3 under the 1940 Act and Rule 498A (including paragraph (j) thereof) under the 1933 Act and any interpretations of those Rules by the Securities and Exchange Commission, its staff, courts, or other appropriate legal authorities. (b) To the extent the terms of this Amendment conflict with the terms of the Participation Agreement, the terms of this Amendment shall control; otherwise, and except as otherwise specifically set forth in this Amendment, the terms of the Participation Agreement shall continue to apply, and shall apply to the duties, responsibilities, rights and obligations of the Parties under and pursuant to this Amendment.
Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5