Boundary revisions Sample Clauses

Boundary revisions notification of Congres- sional committees; publication in Federal Register The map referred to in this section shall be on file and available for public inspection in the of- fices of the National Park Service, Department of the Interior, Washington, District of Colum- bia. After advising the Committee on Natural Resources of the House of Representatives and the Committee on Energy and Natural Re- sources of the Senate in writing, the Secretary of the Interior (hereinafter referred to as the ‘‘Secretary’’) is authorized to make minor revi- sions of the boundaries of the recreation area when necessary by publication of a revised draw- ing or other boundary description in the Federal Register. (Pub. L. 92–592, §§ 1, 3(b)(2), Oct. 27, 1972, 86 Stat. 1308; Pub. L. 103–437, § 6(n)(3), Nov. 2, 1994, 108 Stat. 4586; Pub. L. 106–132, § 1(2), Dec. 7, 1999, 113 Stat. 1681.) Amendments 1999—Subsec. (a)(4). Pub. L. 106–132 added Pub. L. 92–592, § 3(b)(2). See 1972 Amendment note below.
Sample 1Sample 2
AutoNDA by SimpleDocs
Boundary revisions. The Parties agree and acknowledge that changes to the City’s corporate boundaries by annexation or other legal means may occur during the term of this Agreement. As reflected in the Definition of “Boundary” or “Boundaries” above, Developer shall include in the definition of the current Boundary for the purposes of this Project, locations designated by the City for annexation in the 2017-2022 process as reflected on the Boundary Map attached as Exhibit “E”. Developer shall use all commercially reasonable efforts to include any further new locations within the definition of the Boundary, upon mutual agreement of the Parties, within twelve
Sample 1

Related to Boundary revisions

  • Technical Objections No grievance shall be defeated merely because of a technical error, other than time limitations in the processing of the grievance through the grievance procedure. To this end, an arbitrator shall have the power to waive formal procedural irregularities in the processing of the grievance in order to determine the real matter in dispute.

  • General Project Description 2. Substation location.

  • Site Plan It is Licensee’s responsibility before signing this Agreement to ensure that the Site Plan correctly shows the work that Licensee intends to perform, that the Site Plan correctly shows all improvements and equipment that Licensee intends be located on the Use Areas, that the Site Plan shows no work, improvements or equipment outside the Exclusive Areas and Shared Areas properly depicted and labeled on the Boundary Plan, and that all work, improvements and equipment is encompassed within the purposes enumerated in the Standard Terms for that particular Exclusive Area or Shared Area. Any work, improvements or equipment not conforming to all the foregoing is prohibited, even if it is clearly shown on the Site Plan or discussed in the Standard Terms. Any refinement or other change to the Site Plan after Licensor executes this Agreement is void unless Licensee obtains Licensee’s approval of the change pursuant to the plans approval processes set out in the Standard Terms and pursuant to all applicable regulatory requirements.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Escrow Format Specification 3.1. 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.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Classification Plan Revisions A. The Employer will provide to the Union, in writing, any proposed changes to the classification plan including descriptions for newly created classifications. Upon request of the Union, the Employer will bargain, in accordance with Article 37, Mandatory Subjects, the effect(s) of a change to an existing class or newly proposed classification.

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