Code Inspections and Compliance
Code Inspections and Compliance Sample Clauses
Related to Code Inspections and Compliance
Inspections and Testing Each Interconnected Entity shall perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Customer Facility with the Transmission System in a safe and reliable manner. Each Interconnected Entity shall have the right, upon advance written notice, to request reasonable additional testing of an Interconnected Entity’s facilities for good cause, as may be in accordance with Good Utility Practice.
Inspections and Tests 26.1 The Supplier shall at its own expense and at no cost to the Procuring Entity carry out all such tests and/or inspections of the Goods and Related Services as are specified in the SCC.
Response/Compliance with Audit or Inspection Findings A. Grantee must act to ensure its and its Subcontractors’ compliance with all corrections necessary to address any finding of noncompliance with any law, regulation, audit requirement, or generally accepted accounting principle, or any other deficiency identified in any audit, review, or inspection of the Contract and the services and Deliverables provided. Any such correction will be at Grantee’s or its Subcontractor's sole expense. Whether Xxxxxxx's action corrects the noncompliance shall be solely the decision of the System Agency.
Ethics and Compliance This trial will be conducted in accordance with the ethical principles that have their origin in the Declaration of Helsinki and the referenced directives, regulations, guidelines, and/or standards.
Safety Inspection During inspection of County facilities conducted by the State Division of Occupational Safety and Health for the purpose of determining compliance with the California OSHA requirements, an OCEA designated employee shall be allowed to accompany the inspector while the inspector is in the employee's agency/department. The employee so designated shall suffer no loss of pay when this function is performed during the employee's regularly scheduled work hours.
E-Verify Compliance The contractor represents and covenants that the contractor and its subcontractors comply with the requirements of Article 2 of Chapter 64 of the North Carolina General Statutes (NCGS). In this E-Verify Compliance section, "contractor," "its subcontractors," and "comply" shall have the meanings intended by NCGS 160A-20.1(b). The City is relying on this section in entering into this contract. The parties agree to this section only to the extent authorized by law. If this section is held to be unenforceable or invalid in whole or in part, it shall be deemed amended to the extent necessary to make this contract comply with NCGS 160A-20.1(b).
Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.
Inspection and Testing Each Constructing Entity shall cause inspection and testing of the Interconnection Facilities that it constructs in accordance with the provisions of this section. The Construction Parties acknowledge and agree that inspection and testing of facilities may be undertaken as facilities are completed and need not await completion of all of the facilities that a Constructing Entity is building.
Inspection and Tests 3.8.1 The Procuring entity or its representative shall have the right to inspect and/or to test the goods to confirm their conformity to the Contract specifications. The Procuring entity shall notify the tenderer in writing in a timely manner, of the identity of any representatives retained for these purposes.
Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).
