Replacement DB Selection Process Sample Clauses

Replacement DB Selection Process. Concessionaire shall manage, direct and pay for such Replacement DB Selection Process in accordance with the terms set forth in the Settlement Agreement, this Section 7.16.3, and Attachment 2 to Exhibit 13B. The Replacement DB Selection Process, including the solicitation process, timing thereof and selection and evaluation criteria, shall be as set forth or contemplated in Attachment 2 to Exhibit 13B. Such evaluation and selection criteria shall be focused on factors that may include capacity, capability, schedule, and rate structure, in each case as also set forth or contemplated in Attachment 2 to Exhibit 13B. 7.16.3.1 The Replacement DB Selection Process shall contemplate an initial short listing of a few potential candidates for the role of the Replacement DB Contractor. The process for selection of such Shortlisted Candidates is set forth in Attachment 2 to Exhibit 13B. Once selected, the Shortlisted Candidates, in coordination with and subject to the final approval of Owner, will undertake due diligence with respect to the Project. Such due diligence shall include the negotiation of a form of Replacement DB Contract that shall be (a) drafted by Concessionaire, in form substantially similar to the existing Design-Build Contract, including proposed scheduled dates for completion of the D&C Work, and the risk allocation for previously completed D&C Work, such that the Replacement DB Contract will comply with this Agreement, as amended pursuant to the Second Amendment and the Subsequent P3 Amendments, and
Sample 1
AutoNDA by SimpleDocs

Related to Replacement DB Selection Process

  • Selection Process The Mortgage Loans were selected from among the outstanding one- to four-family mortgage loans in the Seller's portfolio at the related Closing Date as to which the representations and warranties set forth in Subsection 9.02 could be made and such selection was not made in a manner so as to affect adversely the interests of the Purchaser;

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Site Selection 5.1.1 If the parties have not designated the street address of the Franchised Location on Exhibit A on the Effective Date, Franchisee shall identify, submit and obtain Franchisor’s prior written approval of the Franchised Location meeting the requirements of this Agreement prior to entering a lease or sublease for the Franchised Location. Franchisee shall provide Franchisor all information required by Franchisor, as determined by Franchisor in Franchisor’s sole determination, necessary for Franchisor to evaluate the Franchised Location. Franchisor shall have ten (10) business days to review Franchisee’s written site proposal for the Franchised Location and notify Franchisee of its approval or disapproval in writing. Franchisor’s failure to respond within ten (10) business days shall signify Franchisor’s disapproval of the site. Franchisor shall not unreasonably withhold Franchisor’s approval of a proposed site for the Franchised Location. 5.1.2 Franchisee must have a site for the Franchised Location approved by Franchisor, receive the opening notice from Franchisor described in Section 5.4 below, and open Franchisee’s Franchised Business for business within six (6) months from the Effective Date, except as otherwise provided in Section 5.1.3 All matters related in any way to Franchisee’s site are Franchisee’s sole responsibility, regardless of any assistance Franchisor may choose to provide. Franchisee is responsible for obtaining any architectural and engineering services required for Franchisee’s facility and for ensuring its compliance with local law. Neither Franchisor, nor any other person or company associated with Franchisor shall have any liability for any site‐related matter. Xxxxxxxxxx agrees not to make any claims against Franchisor and/or any of Franchisor’s affiliates or associates with regard to such matters. 5.1.4 If Franchisor makes a loan to Franchisee for (i) Franchisee’s purchase of the franchise for the Franchised Business; (ii) the remodeling of the Franchised Location; (iii) the transfer of any interest in this franchise or this Agreement; or (iv) any other purpose; Franchisee shall open (or re‐open, as the case may be), the Franchised Business for business within sixty (60) days from the loan origination date.

  • Panel Selection 1. The Parties shall apply the following procedures in selecting a Panel: (a) the Panel shall comprise 3 members; (b) within 15 days following the date of the establishment of the Panel, each Party shall nominate a Panelist; (c) the Parties shall endeavor 2. If a Panelist appointed under this Article resigns or becomes unable to act, a successor Panelist shall be appointed within 30 days in accordance with the selection procedure as prescribed for the appointment of the original Panelist and the successor shall have all the powers and duties of the original Panelist. The work of the Panel shall be suspended during the appointment of the successor Panelist.

  • Selection Procedure 10.2.4.1 Internal applicants shall be defined as all applicants with seniority in accordance with Article 12.5. 10.2.4.2 In filling a posted vacancy, first consideration shall be given to internal applicants who meet the stated qualifications. All Faculty members who meet the stated qualifications for the posted vacancy shall be interviewed by the Selection Committee. Past service and evaluations shall be considered by the Committee. The best qualified candidate shall be recommended for appointment to the position. 10.2.4.3 Where the qualifications of two or more of the applicants are relatively equal, the applicant with the greatest seniority shall be recommended for appointment to the position. 10.2.4.4 In establishing the qualifications, and in evaluating the qualifications and past performance of the applicants, the committee shall act in good faith, in a fair and reasonable manner, and shall not act in an arbitrary or discriminatory fashion. 10.2.4.5 Following the interviews, the committee will submit its recommendations containing a list of qualified candidates in order of preference, through the appropriate Xxxx to the President or delegate. 10.2.4.6 New faculty members shall be appointed only when there are no qualified internal applicants. 10.2.4.7 If there are no qualified internal applicants, the selection committee may consider external applications, in accordance with the procedure outlined above. 10.2.4.8 Internal applicants will be advised as soon as possible of the selection committee's decision that the committee will be considering external applications in accordance with Article 10.2.4.7.

  • Collection Procedure Escrow Agent is hereby authorized to deposit the proceeds of each wire in the Escrow Account.

  • TRANSACTION PROCESS The RFQ for this Lot will contain a deliverable-based Statement of Work (SOW). The RFQ will include, but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote.

  • ONLINE PUBLIC AUCTION PROCESS Bidders may browse through the PAH Website and select the properties they wish to bid online.

  • Single Source Selection Services for tasks in circumstances which meet the requirements of paragraph 3.10 of the Consultant Guidelines for Single Source Selection, may, with the Association's prior agreement, be procured in accordance with the provisions of paragraphs 3.9 through 3.13 of the Consultant Guidelines.

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

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