Conformity with CEQA Project Description and Draft EIR; MMRP Sample Clauses

Conformity with CEQA Project Description and Draft EIR; MMRP. Lead Developer agrees to endeavor to design and plan the Facility in a manner that is consistent with the Project description in the Draft EIR, as well as the draft mitigation measures set forth in the draft EIR, subject to the review and findings of the Planning Department; provided if the EIR is certified by the Planning Commission during the PDA Term, Lead Developer must design and plan the Facility in a manner that is consistent with the Project description in the EIR and comply with any MMRP, to the extent any MMRP requirements apply during the PDA Term. Nothing in this Agreement shall be construed to preclude Lead Developer from proposing, or City and other public agencies from considering or approving Project designs, modifications, or alternatives that avoid or mitigate significant adverse environmental impacts. If the Planning Commission certifies the EIR, the Parties anticipate the Planning Commission would adopt the MMRP at that time. Lead Developer acknowledges and agrees that the MMRP, if adopted, may differ from the draft mitigation measures in the Draft EIR and it will modify its designs and plans accordingly to reflect the requirements of the MMRP.
Sample 1
AutoNDA by SimpleDocs

Related to Conformity with CEQA Project Description and Draft EIR; MMRP

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Conformity with Plan This Agreement is intended to conform in all respects with, and is subject to all applicable provisions of, the Plan. Inconsistencies between this Agreement and the Plan shall be resolved in accordance with the terms of the Plan. In the event of any ambiguity in this Agreement or any matters as to which this Agreement is silent, the Plan shall govern. A copy of the Plan is available upon request to the Administrator.

  • Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.

  • Conformity with EXXXX Filing The Prospectus delivered to the Agent for use in connection with the sale of the Placement Shares pursuant to this Agreement will be identical to the versions of the Prospectus created to be transmitted to the Commission for filing via EXXXX, except to the extent permitted by Regulation S-T.

  • Conformity with XXXXX Filing The Prospectus delivered to the Agent for use in connection with the sale of the Placement Shares pursuant to this Agreement will be identical to the versions of the Prospectus created to be transmitted to the Commission for filing via XXXXX, except to the extent permitted by Regulation S-T.

  • Construction Schedule The progress schedule of construction of the Project as provided by Developer and approved by District.

  • DESCRIPTION OF CONTRACT MODIFICATION This contract modification is made in accordance with Exhibit E-Revised-1, Contractual Terms and Conditions, Section 22. CHANGES, to be made part hereof for all pertinent purposes. The changes are as follows:

  • Conformity Assessment Procedures 1. Each Party shall give positive consideration to accepting the results of conformity assessment procedures of other Parties, even where those procedures differ from its own, provided it is satisfied that those procedures offer an assurance of conformity with applicable technical regulations or standards equivalent to its own procedures. 2. Each Party shall seek to enhance the acceptance of the results of conformity assessment procedures conducted in the territories of other Parties with a view to increasing efficiency, avoiding duplication and ensuring cost effectiveness of the conformity assessments. In this regard, each Party may choose, depending on the situation of the Party and the specific sectors involved, a broad range of approaches. These may include but are not limited to: (a) recognition by a Party of the results of conformity assessments performed in the territory of another Party; (b) recognition of co-operative arrangements between accreditation bodies in the territories of the Parties; (c) mutual recognition of conformity assessment procedures conducted by bodies located in the territory of each Party; (d) accreditation of conformity assessment bodies in the territory of another Party; (e) use of existing regional and international multilateral recognition agreements and arrangements; (f) designating conformity assessment bodies located in the territory of another Party to perform conformity assessment; and (g) suppliers’ declaration of conformity. 3. Each Party shall exchange information with other Parties on its experience in the development and application of the approaches in Paragraph 2(a) to (g) and other appropriate approaches with a view to facilitating the acceptance of the results of conformity assessment procedures. 4. A Party shall, upon request of another Party, explain its reasons for not accepting the results of any conformity assessment procedure performed in the territory of that other Party.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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