Additional Violations Sample Clauses

Additional Violations. For additional violations, Tenant shall be charged a minimum fine of Fifty Dollars ($50.00). Management may, in its discretion, declare the Lease to be in default. Fines for violations are to cover the administrative costs of handling a pet violation but do not cover damages or destruction caused by a violation of this Addendum. Tenant shall remain liable for any and all damages exceeding normal wear and tear to the Unit caused by the pets or animals, and the above fees are not intended to release Tenant of such liability.
Sample 1
AutoNDA by SimpleDocs
Additional Violations. On or about October 19, 2021, the Companies informed CARB that they will violate the Off-Road Regulation, by adding one piece of banned or altered equipment to its fleet, identified by the following EIN: SN5A59. On or about November 2, 2021, the Companies informed CARB that they will violate the Off-Road Regulation, by adding another piece of banned or altered equipment to its fleet, identified by the following EIN: DX3T35. On or about February 21, 2023, the Companies informed CARB that they will violate the Off-Road Regulation, by adding one piece of banned or altered equipment to its fleet, identified by the following EIN: HR3C37. On April 6, 2023, the Companies informed CARB that HR3C37 was purchased to replace DX3T35. DX3T35 broke down and cannot be repaired. DX3T35 has been permanently taken out of service.
Sample 1
Additional Violations. Additional violations of collegiality and meaningful shared governance that were not discussed during the CoC meeting but were shared in other contexts: ● SEPS - The formation of the Curriculum and Instruction Department which was split off from Educational Leadership and Instructional Technology Department. The new department was proposed in October of 2021 and officially announced in January of 2022. Four faculty members were assigned to this new department, and three of those faculty members did not consent to the reassignment. One member did not have a commonality of interest and did not teach courses in the new department. The Faculty Senate and Curriculum Committees did not support this reorganization. The faculty of the original department did not engage in any of the planning for the new department and there was no vote or consensus to form this new department. ● Continued movement to dissolve School of Graduate Studies – according to an email from Xxxxxxx Kostelis dated 10/13/22, the decision to dissolve the School of Graduate Studies was made by Deans and the Office of Academic Affairs. In that message, the Xxxxxxx states that conversations will be held with the Graduate Studies Committee, Program Coordinators, Department Chairs, and the Registrar's Office. A memorandum from Associate Vice President Xxxxxx Xxxxxxx and Xxxxxxx Xxxxxxxx was forwarded to all faculty on 11/1/22 that sought to clarify these decisions and outlined a schedule of past meetings with the aforementioned groups. This memo confirms that only three one-on- one meetings were held with the Chair of the Graduate Studies Committee during the first month of the semester, and that the proposal to dissolve the School of Graduate Studies was presented only once to the full Graduate Studies Committee on 9/22/22, only three weeks before the 10/13/22 campus-wide announcement of the decision. The memo also outlines dates of meetings held subsequent to the 10/13/22 announcement. However, during those meetings, Chairs and Program Coordinators report that they were merely informed of pending changes and not provided with the opportunity to engage in meaningful conversation. It remains apparent that decisions about the dissolution of the School of Graduate Studies have already been made by administrators without meaningful engagement with chairs and faculty and so shared governance continues to be violated. ● Lack of meaningful discussion with faculty regarding the elimination of PINs. In an ...
Sample 1
Additional Violations. On or about October 19, 2021, Tutor Perini Corporation, and O & G Industries, Inc., a Joint Venture, and Frontier Xxxxxx Constructors Inc. and Tutor Perini Corporation, a Joint Venture, informed CARB that they will violate California Code of Regulations, title 13, section 2449, subdivision (d)(6), by adding one piece of banned or altered equipment to its fleet, identified by the following EIN: SN5A59. On or about November 2, 2021, Tutor Perini Corporation, and O & G Industries, Inc., a Joint Venture, and Frontier Xxxxxx Constructors Inc. and Tutor Perini Corporation, a Joint Venture, informed CARB that they will violate California Code of Regulations, title 13, section 2449, subdivision (d)(6), by adding another piece of banned or altered equipment to its fleet, identified by the following EIN: DX3T35.
Sample 1

Related to Additional Violations

  • Repeat Violations Xxxxxxx agrees to comply with all regulatory requirements and acknowledges that repeat violations could result in increased penalties in the future.

  • ALLEGED VIOLATIONS ‌ At its discretion, NRMP will investigate alleged violations of this Agreement, including but not limited to:

  • Reporting Violations a) When appropriate, faculty members will submit timely written communication to their immediate supervisor any condition that comes to their attention that may, in their judgment, pose a threat to the health or safety of any person associated with the District.

  • WAGE VIOLATIONS Contractor represents and warrants that, during the term of this Master Contract and the three (3) year period immediately preceding the award of the Master Contract, it is not determined, by a final and binding citation and notice of assessment issued by the Washington Department of Labor and Industries or through a civil judgment entered by a court of limited or general jurisdiction, to be in willful violation of any provision of Washington state wage laws set forth in RCW chapters 49.46, 49.48, or 49.52.

  • Train Operator Events of Default The following are Train Operator Events of Default:

  • Additional Actions If, at any time after the Effective Time, the Surviving Corporation shall consider or be advised that any deeds, bills of sale, assignments, assurances or any other actions or things are necessary or desirable to vest, perfect or confirm of record or otherwise in the Surviving Corporation its right, title or interest in, to or under any of the rights, properties or assets of Merger Sub or the Company or otherwise carry out this Agreement, the officers and directors of the Surviving Corporation shall be authorized to execute and deliver, in the name and on behalf of Merger Sub or the Company, all such deeds, bills of sale, assignments and assurances and to take and do, in the name and on behalf of Merger Sub or the Company, all such other actions and things as may be necessary or desirable to vest, perfect or confirm any and all right, title and interest in, to and under such rights, properties or assets in the Surviving Corporation or otherwise to carry out this Agreement.

  • Additional Activities I agree that during the period of my employment by the Company I will not, without the Company's express written consent, engage in any employment or business activity which is competitive with, or would otherwise conflict with, my employment by the Company. I agree further that for the period of my employment by the Company and for one (l) year after the date of termination of my employment by the Company I will not induce any employee of the Company to leave the employ of the Company.

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

  • Consequences of Events of Default and Corrective Action If an Event of Default occurs, the Province may, at any time, take one or more of the following actions:

  • Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

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