Failure of Company’s Facilities to Comply with Laws Sample Clauses

Failure of Company’s Facilities to Comply with Laws. Any permit conditions or regulations pertaining to Company’s Facilities within the County is violated.
AutoNDA by SimpleDocs

Related to Failure of Company’s Facilities to Comply with Laws

  • Amendment to Comply with Law The Parties acknowledge that state and federal laws and regulations relating to data security and privacy are rapidly evolving and that amendment of this Agreement may be required to provide procedures to ensure compliance with such developments.

  • Comply with Laws It will comply in all material respects with all applicable laws and orders to which it may be subject if failure so to comply would materially impair its ability to perform its obligations under this Agreement or any Credit Support Document to which it is a party.

  • Failure to comply with directions If the Train Operator fails to comply with any directions given under paragraph 4.1, Network Rail shall be entitled to remove from the Network or Stable any Specified Equipment left on the Network or to instruct a third party to do so and any reasonable costs incurred by Network Rail in taking such steps shall be paid promptly by the Train Operator.

  • Failure to Comply with Arbitrator’s Decision 10.6.1 The award of such Arbitrator shall be final and binding upon the parties.

  • Prohibition on Political Activity with City Funds In accordance with San Francisco Administrative Code Chapter 12.G, Contractor may not participate in, support, or attempt to influence any political campaign for a candidate or for a ballot measure (collectively, “Political Activity”) in the performance of the services provided under this Agreement. Contractor agrees to comply with San Francisco Administrative Code Chapter 12.G and any implementing rules and regulations promulgated by the City’s Controller. The terms and provisions of Chapter 12.G are incorporated herein by this reference. In the event Contractor violates the provisions of this section, the City may, in addition to any other rights or remedies available hereunder, (i) terminate this Agreement, and (ii) prohibit Contractor from bidding on or receiving any new City contract for a period of two (2) years. The Controller will not consider Contractor’s use of profit as a violation of this section.

  • Restricted Use By Outsourcers / Facilities Management, Service Bureaus or Other Third Parties Outsourcers, facilities management or service bureaus retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: 1) Licensee gives notice to Contractor of such party, site of intended use of the Product, and means of access; and 2) such party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and 3) if such party is engaged in the business of facility management, outsourcing, service bureau or other services, such third party will maintain a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non-Disclosure Agreement create or impose any liabilities on the State or Licensee. Any third party with whom a Licensee has a relationship for a state function or business operation, shall have the temporary right to use Product (e.g., JAVA Applets), provided that such use shall be limited to the time period during which the third party is using the Product for the function or business activity.

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Consistency with Federal Laws and Regulations This Agreement shall incorporate by reference Section 22.9 of the CAISO Tariff as if the references to the CAISO Tariff were referring to this Agreement.

  • Compliance with Laws and Regulations A. The Parties shall comply with all applicable laws and regulations including, but not limited to, safety; security; export control; environmental; and suspension and debarment laws and regulations. Access by a Partner to NASA facilities or property, or to a NASA Information Technology (IT) system or application, is contingent upon compliance with NASA security and safety policies and guidelines including, but not limited to, standards on badging, credentials, and facility and IT system/application access.

  • Applicable Laws and Regulations All duly promulgated applicable federal, state and local laws, regulations, rules, ordinances, codes, decrees, judgments, directives, or judicial or administrative orders, permits and other duly authorized actions of any Governmental Authority having jurisdiction over the relevant parties, their respective facilities, and/or the respective services they provide.

Time is Money Join Law Insider Premium to draft better contracts faster.