Contractor’s Documentation Sample Clauses

Contractor’s Documentation. 1. Maintain detailed records of Work completed on a time and material basis. Provide full information required for evaluation of proposed changes, and substantiate costs of changes in the Work. 2. Document each quotation for a change in cost or time with sufficient data allowing evaluation of the quotation. 3. On request, provide additional data to support computations: a. Quantities of products, labor, and equipment b. Taxes, insurance and bonds c. Overhead and profit d. Justification for any change in Contract Time e. Credit for deletions from Contract, similarly documented 4. Support each claim for additional costs, and for Work completed on a time and material basis, with additional information: a. Origin and date of claim b. Dates and times work was performed and by whom
Contractor’s Documentation. The Contractor shall not be required to provide to the Purchaser or the Engineer shop drawings nor any of the Contractor's confidential manufacturing drawings, designs or know-how nor the confidential details of manufacturing practices, processes or operations other than as may be required for purposes of this Contract, in any arbitration, dispute resolution, court proceedings or by the Law.

Related to Contractor’s Documentation

  • Contractor’s Documents Any licensing and maintenance agreement, or any order-specific agreement or document, including any pre-installation, linked or “click through” agreement that is allowed by, referenced within or incorporated within the Contract whenever the Contract is used for a State procurement, whether directly by the Contractor or through a Contractor’s agent, subcontractor or reseller, is agreed to only to the extent the terms within any such agreement or document do not conflict with the Contract or applicable Minnesota or Federal law, and only to the extent that the terms do not modify, diminish or derogate the terms of the Contract or create an additional financial obligation to the State. Any such agreement or document must not be construed to deprive the State of its sovereign immunity, or of any legal requirements, prohibitions, protections, exclusions or limitations of liability applicable to this Contract or afforded to the State by Minnesota law. A State employee’s decision to choose “accept” or an equivalent option associated with a “click- through” agreement does not constitute the State’s concurrence or acceptance of terms, if such terms are in conflict with this section.

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

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

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

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. Claims can arise, under certain types of insurance contract, long after the expiry of the policy. It is therefore important that you retain and keep safely all documents associated with your policy.

  • Medical Documentation The teacher must supply a letter from a medical 3 doctor, who treated the patient, stating that in his/her opinion, there is a strong 4 probability that the illness was contracted at school.

  • 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: a) Readability, and DocuSign Envelope ID: CA9F0A59-74CF-45EC-A0BA-DA5EDEFB2344 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 (FONSI), 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: CA9F0A59-74CF-45EC-A0BA-DA5EDEFB2344 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.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • 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 or 2024, as applicable and as amended