Records and Documentation The Sub-Recipient agrees to make available to AAAPP staff and/or any party designated by the AAAPP any and all contract related records and documentation. The Sub-Recipient shall ensure the collection and maintenance of all program related information and documentation on any such system designated by the AAAPP. Maintenance includes valid exports and backups of all data and systems according to AAAPP standards.
Personnel Requirements and Documentation Grantee will; 1. maintain current personnel documentation on each employee. All documents must be factual and accurate. Health-related information must be stored separately with restricted access as appropriate under Tex. Gov. Code §552.102. Training records may be stored separately from the main personnel file but must be easily accessible upon request. Required documentation includes the following, as applicable: i. A copy of the current job description signed by the employee; ii. Application or resume with documentation of required qualifications and verification of required credentials; iii. Verification of work experience; iv. Annual performance evaluations; v. Personnel data that includes date hired, rate of pay, and documentation of all pay increases and bonuses; vi. Documentation of appropriate screening and/or background checks, to include probation or parole documentation; vii. Signed documentation of initial and other required training; and viii. Records of any disciplinary actions. 2. document authentication must include signature, credentials when applicable, and date. If the document relates to past activity, the date of the activity must also be recorded. Documentation must be permanent and legible. When it is necessary to correct a required document, the error must be marked through with a single line, dated, and initialed by the writer.
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.
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.
Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.