PWA Requirement and Documentation Sample Clauses

PWA Requirement and Documentation. (a) Seller shall, and shall cause its Affiliates to, (i) comply with the PWA Requirements with respect any Work on the Project (including any warranty work) that constitutes CAR Work, and (ii) include the requirement to comply, and to require all Contractors and Subcontractors to comply, with the PWA Requirements in each EPC Contract, and any other Contract pursuant to which any contractor or subcontractor of any tier will perform Work on the Project (including any warranty work) that constitutes CAR Work, including by requiring all Contractors and Subcontractors of any tier to include flow down provisions consistent with the requirements of this Section 2.13 in all Contracts with any Subcontractor. (b) Seller shall collect, prepare, and maintain documentation sufficient to establish compliance with the PWA Requirements for all Work on the Project (including any warranty work) that constitutes CAR Work. Such documentation shall include, for each calendar month, beginning with the first calendar month in which any Laborer or Mechanic (including any Qualified Apprentice) performs CAR Work (collectively, “PWA Documentation”): (i) With respect to the Prevailing Wage requirements, the following for each Laborer and Mechanic (including each Qualified Apprentice) Employed by Seller or any of its Affiliates or by any Contractor or Subcontractor of any tier in the CAR Work: (A) identifying information, including the name, social security or tax identification number, address, telephone number and email address, and job title; (B) the labor classifications(s) applied to the Laborer or Mechanic for determining the Prevailing Wage and documentation supporting the applicable classification, including the applicable Wage Determination and communications with the DOL, Wage and Hour Division regarding the Wage Determination; (C) the hourly rate(s) of wages paid (including rates of contributions or costs for bona fide fringe benefits or cash equivalents thereof) for each applicable labor classification; (D) records to support any contribution irrevocably made on behalf of a Laborer or Mechanic to a trustee or other third person pursuant to a bona fide fringe benefit program, and the rate of costs that were reasonably anticipated in providing bona fide fringe benefits to Laborers and Mechanics pursuant to an enforceable commitment to carry out a plan or program described in 40 U.S.C. 3141(2)(B), including records demonstrating that the enforceable commitment was provided in...
AutoNDA by SimpleDocs

Related to PWA Requirement and Documentation

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

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

  • Documentation Requirements ODM shall pay the MCP after it receives sufficient documentation, as determined by ODM, detailing the MCP’s Ohio Medicaid-specific liability for the Annual Fee. The MCP shall provide documentation that includes the following: 1. Total premiums reported on IRS Form 8963;

  • Other Required Documentation All other documents and legal matters in connection with the transactions contemplated by this Amendment shall have been delivered or executed or recorded and shall be in form and substance satisfactory to Agent.

  • CREDIT AND COLLATERAL REQUIREMENTS The applicable credit and collateral requirements are specified on the Cover Sheet.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Abbreviated Documentation Requirements Compile and submit:

  • Applicable Law and Construction This Lease may be executed in counterparts, shall be construed as a sealed instrument, and shall be governed exclusively by the provisions hereof and by the laws of the state where the Property is located without regard to principles of choice of law or conflicts of law. A facsimile signature to this Lease shall be sufficient to prove the execution by a party. If any provisions shall to any extent be invalid, the remainder shall not be affected. Other than contemporaneous instruments executed and delivered of even date, if any, this Lease contains all of the agreements between Landlord and Tenant relating in any way to the Premises and supersedes all prior agreements and dealings between them. There are no oral agreements between Landlord and Tenant relating to this Lease or the Premises. This Lease may be amended only by instrument in writing executed and delivered by both Landlord and Tenant. The provisions of this Lease shall bind Landlord and Tenant and their respective successors and assigns, and shall inure to the benefit of Landlord and its successors and assigns and of Tenant and its permitted successors and assigns, subject to Article 13. The titles are for convenience only and shall not be considered a part of this Lease. This Lease shall not be construed more strictly against one party than against the other merely by virtue of the fact that it may have been prepared primarily by counsel for one of the parties, it being recognized that both Landlord and Tenant have contributed substantially and materially to the preparation of this Lease. If Tenant is granted any extension or other option, to be effective the exercise (and notice thereof) shall be unconditional; and if Tenant purports to condition the exercise of any option or to vary its terms in any manner, then the purported exercise shall be ineffective. The enumeration of specific examples of a general provision shall not be construed as a limitation of the general provision. Unless a party’s approval or consent is required by the express terms of this Lease not to be unreasonably withheld, such approval or consent may be withheld in the party’s sole discretion. The submission of a form of this Lease or any summary of its terms shall not constitute an offer by Landlord to Tenant; but a leasehold shall only be created and the parties bound when this Lease is executed and delivered by both Landlord and Tenant and approved by the holder of any mortgage of the Premises having the right to approve this Lease. Nothing herein shall be construed as creating the relationship between Landlord and Tenant of principal and agent, or of partners or joint venturers or any relationship other than landlord and tenant. This Lease and all consents, notices, approvals and all other related documents may be reproduced by any party by any electronic means or by facsimile, photographic, microfilm, microfiche or other reproduction process and the originals may be destroyed; and each party agrees that any reproductions shall be as admissible in evidence in any judicial or administrative proceeding as the original itself (whether or not the original is in existence and whether or not reproduction was made in the regular course of business), and that any further reproduction of such reproduction shall likewise be admissible. If any payment in the nature of interest provided for in this Lease shall exceed the maximum interest permitted under controlling law, as established by final judgment of a court, then such interest shall instead be at the maximum permitted interest rate as established by such judgment.

  • Required Documentation The AGENCY is responsible for ensuring that all documents required by this Contract are current and available for the COUNTY’S review upon request. These documents may include, but are not limited to, certificate(s) of insurance, job descriptions and background check confirmations of staff.

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

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