PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations.
OFAC Compliance (a) Tenant represents and warrants that (a) Tenant and each person or entity owning an interest in Tenant is (i) not currently identified on the Specially Designated Nationals and Blocked Persons List maintained by the Office of Foreign Assets Control, Department of the Treasury (“OFAC”) and/or on any other similar list maintained by OFAC pursuant to any authorizing statute, executive order or regulation (collectively, the “List”), and (ii) not a person or entity with whom a citizen of the United States is prohibited to engage in transactions by any trade embargo, economic sanction, or other prohibition of United States law, regulation, or Executive Order of the President of the United States, (b) none of the funds or other assets of Tenant constitute property of, or are beneficially owned, directly or indirectly, by any Embargoed Person (as hereinafter defined), (c) no Embargoed Person has any interest of any nature whatsoever in Tenant (whether directly or indirectly), (d) none of the funds of Tenant have been derived from any unlawful activity with the result that the investment in Tenant is prohibited by law or that the Lease is in violation of law, and (e) Tenant has implemented procedures, and will consistently apply those procedures, to ensure the foregoing representations and warranties remain true and correct at all times. The term “
HIPAA Compliance If this Contract involves services, activities or products subject to the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Contractor covenants that it will appropriately safeguard Protected Health Information (defined in 45 CFR 160.103), and agrees that it is subject to, and shall comply with, the provisions of 45 CFR 164 Subpart E regarding use and disclosure of Protected Health Information.
DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).
CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.
CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.
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”).
OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.
Compliance Requirements K. If using volunteers as provided for in this Contract during FY19, which encompasses the Contract term of July 1, 2019 to June 30, 2020, then the Grantee must either:
ERISA Compliance The Company and its subsidiaries and any “employee benefit plan” (as defined under the Employee Retirement Income Security Act of 1974, as amended, and the regulations and published interpretations thereunder (collectively, “ERISA”)) established or maintained by the Company, its subsidiaries or their “ERISA Affiliates” (as defined below) are in compliance in all material respects with ERISA. “ERISA Affiliate” means, with respect to the Company or any of its subsidiaries, any member of any group of organizations described in Sections 414(b), (c), (m) or (o) of the Internal Revenue Code of 1986, as amended, and the regulations and published interpretations thereunder (the “Code”) of which the Company or such subsidiary is a member. No “reportable event” (as defined under ERISA) has occurred or is reasonably expected to occur with respect to any “employee benefit plan” established or maintained by the Company, its subsidiaries or any of their ERISA Affiliates. No “employee benefit plan” established or maintained by the Company, its subsidiaries or any of their ERISA Affiliates, if such “employee benefit plan” were terminated, would have any “amount of unfunded benefit liabilities” (as defined under ERISA). Neither the Company, its subsidiaries nor any of their ERISA Affiliates has incurred or reasonably expects to incur any liability under (i) Title IV of ERISA with respect to termination of, or withdrawal from, any “employee benefit plan” or (ii) Sections 412, 4971, 4975 or 4980B of the Code. Each employee benefit plan established or maintained by the Company, its subsidiaries or any of their ERISA Affiliates that is intended to be qualified under Section 401(a) of the Code is so qualified and nothing has occurred, whether by action or failure to act, which would cause the loss of such qualification.
