Compliance With SRS Incident Command Policy
Compliance With SRS Incident Command Policy Sample Clauses
Related to Compliance With SRS Incident Command Policy
Compliance with Executive Orders Concerning Ethics The Contractor warrants that he and his firm have complied in all respects with the Governor’s Executive Orders concerning ethics matters, including, but not limited to, Executive Order dated January 13, 2003 (establishing Code of Ethics for Executive Branch Officers and Employees, including provisions governing former officers and employees); Executive Order dated October 1, 2003 (governing vendors to state agencies and disclosure and registration of lobbyists); and O.C.G.A. Sections 21-5-70(5), 21-5-71 and 21-5-73, all as amended effective January 9, 2006 (requiring registration and disclosure filings by state agency vendor lobbyists). In this regard, the Contractor certifies that any lobbyist employed or retained by the Contractor or his firm has both registered and made the required disclosures required by the Executive Orders, as amended.
Compliance with Consensus Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-‐policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”).
Compliance with Policies Each Individual Limited Partner hereby agrees that he shall comply with all policies and procedures adopted by any member of the Och-Ziff Group or which Limited Partners are required to observe by law, or by any recognized stock exchange, or other regulatory body or authority.
Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).
Compliance with Federal Law Contractor shall comply with all applicable federal laws, including, without limitation, those set forth in Exhibit D, which is attached and incorporated into this Contract by this reference.
Compliance with Rules To comply with, and to require the Contractors to comply with, all rules, regulations, ordinances and laws bearing on the conduct of the work on the Improvements, including the requirements of any insurer issuing coverage on the Project and the requirements of any applicable supervising boards of fire underwriters.
Compliance with Federal Law, Regulations, and Executive Orders This is an acknowledgement that FEMA financial assistance will be used to fund the contract only. The contractor will comply will all applicable federal law, regulations, executive orders, FEMA policies, procedures, and directives.
Compliance with Warning Regulations The Parties agree that Xxxxxx Xxxxxx shall be deemed to be in compliance with this Settlement Agreement by either adhering to §§ 2.3 and 2.4 of this Settlement Agreement or by complying with warning requirements adopted by the State of California’s Office of Environmental Health Hazard Assessment (“OEHHA”) applicable to the product and the exposure at issue after the Effective Date.
Compliance with ERISA (i) Each employee benefit plan, within the meaning of Section 3(3) of the Employee Retirement Income Security Act of 1974, as amended (“ERISA”), for which the Company or any member of its “Controlled Group” (defined as any organization which is a member of a controlled group of corporations within the meaning of Section 414 of the Internal Revenue Code of 1986, as amended (the “Code”)) would have any liability (each, a “Plan”) has been maintained in compliance with its terms and the requirements of any applicable statutes, orders, rules and regulations, including but not limited to ERISA and the Code, except for noncompliance that could not reasonably be expected to result in material liability to the Company or its subsidiaries; (ii) no prohibited transaction, within the meaning of Section 406 of ERISA or Section 4975 of the Code, has occurred with respect to any Plan excluding transactions effected pursuant to a statutory or administrative exemption that could reasonably be expected to result in a material liability to the Company or its subsidiaries; (iii) for each Plan that is subject to the funding rules of Section 412 of the Code or Section 302 of ERISA, the minimum funding standard of Section 412 of the Code or Section 302 of ERISA, as applicable, has been satisfied (without taking into account any waiver thereof or extension of any amortization period) and is reasonably expected to be satisfied in the future (without taking into account any waiver thereof or extension of any amortization period); (iv) the fair market value of the assets of each Plan exceeds the present value of all benefits accrued under such Plan (determined based on those assumptions used to fund such Plan); (v) no “reportable event” (within the meaning of Section 4043(c) of ERISA) has occurred or is reasonably expected to occur that either has resulted, or could reasonably be expected to result, in material liability to the Company or its subsidiaries; (vi) neither the Company nor any member of the Controlled Group has incurred, nor reasonably expects to incur, any liability under Title IV of ERISA (other than contributions to the Plan or premiums to the PBGC, in the ordinary course and without default) in respect of a Plan (including a “multiemployer plan”, within the meaning of Section 4001(a)(3) of ERISA); and (vii) there is no pending audit or investigation by the Internal Revenue Service, the U.S. Department of Labor, the Pension Benefit Guaranty Corporation or any other governmental agency or any foreign regulatory agency with respect to any Plan that could reasonably be expected to result in material liability to the Company or its subsidiaries. None of the following events has occurred or is reasonably likely to occur: (x) a material increase in the aggregate amount of contributions required to be made to all Plans by the Company or its subsidiaries in the current fiscal year of the Company and its subsidiaries compared to the amount of such contributions made in the Company and its subsidiaries’ most recently completed fiscal year; or (y) a material increase in the Company and its subsidiaries’ “accumulated post-retirement benefit obligations” (within the meaning of Statement of Financial Accounting Standards 106) compared to the amount of such obligations in the Company and its subsidiaries’ most recently completed fiscal year.
Compliance with State Law The Business Associate acknowledges that by accepting the PHI from Covered Entity, it becomes a holder of medical information under the MCMRA and is subject to the provisions of that law. If the HIPAA Privacy or Security Rules and the MCMRA conflict regarding the degree of protection provided for PHI, Business Associate shall comply with the more restrictive protection requirement.
