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 County, 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 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: i. Readability, and ii. Use of evidence and data in documents to support conclusions. Upon request by the State or the County, the Engineer shall provide documentation that the QA/QC reviews were performed by qualified staff. a. 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. b. 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 County. 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.
Design Development Documents See Section 2, Part 1, Article 2.1.5.
Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.
Reverse Engineering The Customer must not reverse assemble or reverse compile or directly or indirectly allow or cause a third party to reverse assemble or reverse compile the whole or any part of the software or any products supplied as a part of the Licensed System.