Environmental Specification Documentation Sample Clauses

Environmental Specification Documentation. Cheniere Creole Trail Pipeline Right-of-Way Construction Stipulations dated 9/15/06
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Environmental Specification Documentation

  • ENVIRONMENTAL DOCUMENTATION Each environmental service provided by the Engineer shall have a deliverable. Deliverables shall summarize the methods used for the environmental services, and shall summarize the results achieved. The summary of results shall be sufficiently detailed to provide satisfactory basis for thorough review by the State, The Federal Highway Administration (FHWA), and (where applicable) agencies with regulatory oversight. All deliverables shall meet regulatory requirements for legal sufficiency, and shall adhere to the requirements for reports enumerated in the State’s NEPA MOU. a. Quality Assurance/Quality Control Review For each deliverable, the Engineer shall perform quality assurance quality control (QA/QC) reviews of environmental documents and on other supporting environmental documentation to determine whether documents conform with: 1) Current Environmental Compliance Toolkit guidance published by the State’s Environmental Affairs Division and in effect as of the date of receipt of the documents or documentation to be reviewed; 2) Current state and federal laws, regulations, policies, guidance, agreements, and memoranda of understanding between the State and other state or federal agencies; and 3) FHWA and American Association of State Highway and Transportation Officials (AASHTO) guidelines contained in “Improving the Quality of Environmental Documents, A Report of the Joint AASHTO and American Council of Engineering Companies (ACEC) Committee in Cooperation with the Federal Highway Administration” (May 2006) for: DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520 a) Readability, and b) Use of evidence and data in documents to support conclusions. Upon request by the State, the Engineer shall provide documentation that the QA/QC reviews were performed by qualified staff. b. Deliverables shall contain all data acquired during the environmental service. All deliverables shall be written to be understood by the public and must be in accordance with the State’s Environmental Toolkit guidance, documentation standards, current guidelines, policies and procedures. c. Electronic versions of each deliverable must be written in software which is compatible to the State and must be provided in a changeable format for future use by the State. The Engineer shall supplement all hard copy deliverables with electronic copies in searchable Adobe Acrobat™ (.pdf) format, unless another format is specified. Each deliverable shall be a single, searchable .pdf file that mirrors the layout and appearance of the physical deliverable. The Engineer shall deliver the electronic files on CD-R, CD-RW media in Microsoft Windows format, or through the ftp site. d. When the environmental service is to apply for a permit (e.g., United States Coast Guard (USCG) or United States Army Corps of Engineers (USACE), the permit and all supporting documentation shall be the deliverable. e. Submission of Deliverables 1) Deliverables shall consist of reports of environmental services performed in addition to a Categorical Exclusion (CE) determination form and supporting documentation including the required form or Environmental Assessment (EA) document, when applicable. 2) All deliverables must comply with all applicable state and federal environmental laws, regulations and procedures and include all items listed in the Environmental Document Review Checklist and the Administrative Completeness Review Checklist. 3) On the cover page of each environmental assessment (EA), finding of no significant impact (XXXXX), environmental impact statement (EIS), and record of decision (ROD) prepared under the authority granted by this MOU, and for any memorandum corresponding to any CE determination it makes, the Engineer shall insert the following language in a way that is conspicuous to the reader or include it in a CE project record: "The environmental review, consultation, and other actions required by applicable DocuSign Envelope ID: F9E4AA24-4672-4529-8EFA-00D1CA218520 Federal environmental laws for this project are being, or have been, carried-out by TxDOT pursuant to 23 U.S.C. 327 and a Memorandum of Understanding dated December 16, 2014, and executed by FHWA and TxDOT." f. The State shall provide the State’s and other agency comments on draft deliverables to the Engineer. The Engineer shall revise the deliverable: 1) to include any State commitments, findings, agreements, or determinations (e.g., wetlands, endangered species consultation, Section 106, or Section 4(f)), required for the Transportation Activity as specified by the State; 2) to incorporate the results of public involvement and agency coordination; 3) to reflect mitigation measures resulting from comments received or changes in the Transportation Activity; and 4) include with the revised document a comment response form (matrix) in the format provided by the State. g. All photographs shall be 3.5” x 5” color presentation printed on matte finish photographic paper or 3.5” x 5” color presentation printed on matte white, premium or photo quality laser or inkjet paper. All photographs shall be well focused and clearly depict details relevant to an evaluation of the project area. Provision of photographs shall be one original print of each image or electronic presentations of comparable quality. Comparable quality electronic photograph presentations shall be at least 1200 x 1600 pixel resolution. Photographs shall be attached to separately labeled pages that clearly identify project name, project identification (ID) number, address or Universal Transverse Mercator (UTM) of resource, description of the picture and direction of the photographic view. In addition to the hard-copy prints, an electronic version of each will be submitted with the same identification information as the hard-copy.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

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

  • Construction Document Phase 1.4.1 Based on the approved Design Development Documents, Guaranteed Maximum Price, coordinated models and any further adjustments in the scope or quality of the Project or in the Amount Available for the Construction Contract authorized by the Owner, the Architect/Engineer shall prepare, for approval by the Owner and review by the Construction Manager, Construction Documents consisting of Drawings, Schedules and Specifications derived from the model(s) in accordance with Owner’s written requirements setting forth in detail the requirements for construction of the Project, including, without limitation, the BIM Execution Plan and “Facility Design Guidelines”. The Plans, Drawings and Specifications for the entire Project shall be so prepared that same will call for the construction of the building and related facilities, together with its built-in permanent fixtures and equipment which will cost not more than the Guaranteed Maximum Price accepted by Owner, or the Amount Available for the Construction Contract established by Owner if no Guaranteed Maximum Price proposal has been accepted by Owner. The Architect/Engineer will be responsible for managing the design to stay within such Guaranteed Maximum Price proposal or Amount Available for the Construction Contract. The Architect/Engineer shall review the Construction Documents as they are being prepared at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Construction Documents. The Architect/Engineer shall provide the Construction Manager with a compact disc containing documents and data files derived from the model to assist the Construction Manager in fulfilling its responsibilities to the Owner. 1.4.2 As a part of Construction Documents Phase, Architect/Engineer shall accomplish model coordination, aggregation and “clash detection” to remove conflicts in design between systems, structures and components. Architect/Engineer shall demonstrate and provide written assurance to Owner that all conflicts/collisions between models have been resolved. 1.4.3 The Architect/Engineer shall consult with the Owner and Construction Manager on matters such as construction phasing and scheduling, bid or proposal alternates, liquidated damages, the construction contract time period, and other construction issues appropriate for the Project. The Architect/Engineer shall assist the Owner and Construction Manager in the preparation of the necessary bidding information, bidding forms, RFP information, and RFP forms, and the Conditions of the Contract. 1.4.4 The Architect/Engineer shall assist the Owner in connection with the Owner’s responsibility and procedures for obtaining approval of all building and accessibility authorities having jurisdiction over the Project. 1.4.5 The Architect/Engineer shall provide coordination and inclusion of sequence of operations for all operable systems in the facility as defined by Owner during Design Development. 1.4.6 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments. 1.4.7 The Architect/Engineer shall participate in a final review of the Construction Documents and model(s) with the Owner and Construction Manager at the Project location or other location specified by Owner in the State of Texas. Prior to the Owner’s approval of the Construction Documents, the Architect/Engineer shall incorporate such changes as are necessary to satisfy the Owner’s review comments. 1.4.8 Before proceeding into the Bidding and Proposal Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Construction Documents and approval of the Final Amount Available for the Construction Contract as approved by the Board of Regents.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

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

  • Construction Documents Phase Bidding or Negotiation Phase:

  • Construction Documents The architectural and engineering documents setting forth the design for the Project prepared by the Design Professional. Construction Documents include, but are not limited to, the Specifications, the Drawings, the Supplementary Conditions, the General Conditions, and all Addenda.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

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