Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
Project Documents In addition to any other pertinent and necessary Project documents, the following documents shall be used in the development of the Project: A. TxDOT 2011 Texas Manual of Uniform Traffic Control Devices for Streets and Highways, including latest revisions B. Texas Department of Transportation's Standard Specifications for Construction of Highways, Streets, and Bridges, 2014 (English units)
Construction Plans Tenant shall prepare final plans and specifications for the Tenant Improvements that (a) are consistent with and are logical evolutions of the Approved Schematic Plans and (b) incorporate any other Tenant-requested (and Landlord-approved) Changes (as defined below). As soon as such final plans and specifications ("Construction Plans") are completed, Tenant shall deliver the same to Landlord for Landlord's approval, which approval shall not be unreasonably withheld, conditioned or delayed. All such Construction Plans shall be submitted by Tenant to Landlord in electronic .pdf, CADD and full-size hard copy formats, and shall be approved or disapproved by Landlord within ten (10) business days after delivery to Landlord. Landlord's failure to respond within such ten (10) business day period shall be deemed approval by Landlord. If the Construction Plans are disapproved by Landlord, then Landlord shall notify Tenant in writing of its objections to such Construction Plans, and the parties shall confer and negotiate in good faith to reach agreement on the Construction Plans. Promptly after the Construction Plans are approved by Landlord and Tenant, two (2) copies of such Construction Plans shall be initialed and dated by Landlord and Tenant, and Tenant shall promptly submit such Construction Plans to all appropriate Governmental Authorities for approval. The Construction Plans so approved, and all change orders approved (to the extent required) by Landlord, are referred to herein as the "Approved Plans."
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.
Material Project Documents (a) The Company shall at all times (i) perform and observe all of the covenants under the Material Project Documents to which it is a party and take reasonable actions to enforce all of its rights thereunder, other than to the extent the same could not reasonably be expected to have a Material Adverse Effect, (ii) subject to the provisions of clause (b) of this Section 9.8, maintain the System Leases (other than Leases constituting System Leases only pursuant to clause (5) of the definition thereof) in full force and effect, and (iii) maintain the Leases (other than the System Leases referred to in the foregoing clause (ii) of this Section 9.8(a)) to which it or any of its Subsidiaries is a party in full force and effect, except to the extent the same could not reasonably be expected to have a Material Adverse Effect. (b) If the term of a Lease with the Company or one of its Subsidiaries expires and the Qualified Lessee under such Lease has either ceased operating the related assets or has ceased paying rent as required under the applicable Lease, the Company shall, or shall cause a Subsidiary, as applicable, to enter into a supplement or a new Lease with respect to the related leasehold assets with a Qualified Lessee that provides for rent that, when combined with all other expected revenue, will, in the reasonable judgment of the Company, as of the commencement date of such supplement or new Lease, generate sufficient revenue to satisfy the requirements of Section 9.9 and will not otherwise result in a materially worse position for the Company as compared to the terms of the applicable expired Lease. Each such new Lease shall have a term of at least five years. Notwithstanding the foregoing, if (i) such expired Lease relates to transmission and/or distribution assets that are not generating significant revenue, (ii) the failure to renew such Lease would not constitute a Material Adverse Effect and (iii) the Company reasonably believes it will generate sufficient revenue and hold sufficient assets (without giving effect to the leasehold assets with respect to such Lease) to satisfy the requirements of Section 9.9, then this Section 9.8(b) will not require a supplement or new lease with respect to such leasehold assets.
Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.
Project Implementation The Borrower shall:
Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.
Project Agreements Provided that where the company commences work on a project where a site agreement exists to which the company is contractually obligated or where a site agreement exists between the union and the client or their agent that provides for higher rates of pay and conditions, the conditions contained in any such site agreement will take precedence over this Agreement for the duration of the project.
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.
