Notification of Significant Occurrences Sample Clauses

Notification of Significant Occurrences. 1. If any specific event or conjunction of circumstances threatens the successful completion of this project, in whole or in part, including where relevant, timely completion of milestones or other program requirements, the Contractor agrees to submit to the State Agency within three (3) calendar days of becoming aware of the occurrence or of such problem, a written description thereof together with a recommended solution thereto.
AutoNDA by SimpleDocs
Notification of Significant Occurrences. If any specific event or conjunction of circumstances threatens the successful completion of this project, in whole or in part, including where relevant, timely completion of milestones or other program requirements, the Recipient agrees to submit to the State Agency within three (3) calendar days of becoming aware of the occurrence or of such problem, a written description thereof together with a recommended solution thereto. The Recipient shall immediately notify in writing the program manager assigned to the Purchase Order Agreements of any unusual incident, occurrence, or event that involves the staff, volunteers, directors or officers of the Recipient, any subrecipient or program participant funded through the Purchase Order Agreements, including but not limited to the following: death or serious injury; an arrest or possible criminal activity that could impact the successful completion of this project; any destruction of property; significant damage to the physical plant of the Recipient; or other matters of a similarly serious nature.
Notification of Significant Occurrences. 1. ,I DQ\ VSHFLILF HYHQW RU FRQMXQFWLRQ RI FLUFXPVWDQFHV WKUHDWHQV WKH VXFFHVVIXO FRPSOHWLRQ RI WKLV SURMHFW, LQ ZKROH RU LQ SDUW, LQFOXGLQJ ZKHUH UHOHYDQW, WLPHO\ FRPSOHWLRQ RI PLOHVWRQHV RU RWKHU SURJUDP UHTXLUHPHQWV, WKH &RQWUDFWRU DJUHHV WR VXEPLW WR WKH 6WDWH $JHQF\ ZLWKLQ WKUHH (3) FDOHQGDU GD\V RI EHFRPLQJ DZDUH RI WKH RFFXUUHQFH RU RI VXFK SUREOHP, D ZULWWHQ GHVFULSWLRQ WKHUHRI WRJHWKHU ZLWK D UHFRPPHQGHG VROXWLRQ WKHUHWR. 2. 7KH &RQWUDFWRU VKDOO LPPHGLDWHO\ QRWLI\ LQ ZULWLQJ WKH SURJUDP PDQDJHU DVVLJQHG WR WKH 0DVWHU &RQWUDFW RI DQ\ XQXVXDO LQFLGHQW, RFFXUUHQFH, RU HYHQW WKDW LQYROYHV WKH VWDII, YROXQWHHUV, GLUHFWRUV RU RIILFHUV RI WKH &RQWUDFWRU, DQ\ VXEFRQWUDFWRU RU SURJUDP SDUWLFLSDQW IXQGHG WKURXJK WKH 0DVWHU &RQWUDFW, LQFOXGLQJ EXW QRW OLPLWHG WR WKH IROORZLQJ: GHDWK RU VHULRXV LQMXU\; DQ DUUHVW RU SRVVLEOH FULPLQDO DFWLYLW\ WKDW FRXOG LPSDFW WKH VXFFHVVIXO FRPSOHWLRQ RI WKLV SURMHFW; DQ\ GHVWUXFWLRQ RI SURSHUW\; VLJQLILFDQW GDPDJH WR WKH SK\VLFDO SODQW RI WKH &RQWUDFWRU; RU RWKHU PDWWHUV RI D VLPLODUO\ VHULRXV QDWXUH.
Notification of Significant Occurrences. If any specific event or conjunction of circumstances threatens the successful completion of this project, in whole or in part, including where relevant, timely completion of milestones or other program requirements, the Contractor agrees to submit to DHSES within three (3) calendar days of becoming aware of the occurrence or of such problem, a written description thereof together with a recommended solution thereto. The Contractor shall immediately notify in writing the program manager assigned to the Contract of any unusual incident, occurrence, or event that involves the staff, volunteers, directors or officers of the Contractor, any subcontractor or program participant funded through the Contract, including but not limited to the following: death or serious injury; an arrest or possible criminal activity that could impact the successful completion of this project; any destruction of property; significant damage to the physical plant of the Contractor; or other matters of a similarly serious nature. ADDITIONAL CONTRACTOR OBLIGATIONS, REPRESENTATIONS AND WARRANTIES

Related to Notification of Significant Occurrences

  • Notification of Default (a) Each Obligor shall notify the Agent of any Default (and the steps, if any, being taken to remedy it) promptly upon becoming aware of its occurrence (unless that Obligor is aware that a notification has already been provided by another Obligor).

  • Return or Destruction of Confidential Information If an Interconnection Party provides any Confidential Information to another Interconnection Party in the course of an audit or inspection, the providing Interconnection Party may request the other party to return or destroy such Confidential Information after the termination of the audit period and the resolution of all matters relating to that audit. Each Interconnection Party shall make Reasonable Efforts to comply with any such requests for return or destruction within ten days of receiving the request and shall certify in writing to the other Interconnection Party that it has complied with such request.

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Independence from Material Breach Determination Except as set forth in Section X.D.1.c, these provisions for payment of Stipulated Penalties shall not affect or otherwise set a standard for OIG’s decision that CHSI has materially breached this CIA, which decision shall be made at OIG’s discretion and shall be governed by the provisions in Section X.D, below.

  • Notice of Event of Default If the Mortgagee shall have Actual Knowledge of an Event of Default or of a Default arising from a failure to pay Rent, the Mortgagee shall give prompt written notice thereof to the Owner Trustee, the Owner Participant, Lessee, and each Note Holder. Subject to the terms of Sections 2.13, 4.03, 4.04, 4.08, 5.02 and 5.03 hereof, the Mortgagee shall take such action, or refrain from taking such action, with respect to such Event of Default or Default (including with respect to the exercise of any rights or remedies hereunder) as the Mortgagee shall be instructed in writing by a Majority in Interest of Note Holders. Subject to the provisions of Section 5.03, if the Mortgagee shall not have received instructions as above provided within 20 days after mailing notice of such Event of Default to the Note Holders, the Mortgagee may, subject to instructions thereafter received pursuant to the preceding provisions of this Section 5.01, take such action, or refrain from taking such action, but shall be under no duty to take or refrain from taking any action, with respect to such Event of Default or Default as it shall determine advisable in the best interests of the Note Holders; PROVIDED, HOWEVER, that the Mortgagee may not sell the Aircraft or any Engine without the consent of a Majority in Interest of Note Holders. For all purposes of this Trust Indenture, in the absence of Actual Knowledge on the part of the Mortgagee, the Owner Trustee or the Owner Participant, the Mortgagee, the Owner Trustee or the Owner Participant, as the case may be, shall not be deemed to have knowledge of a Default or an Event of Default (except, in the case of the Mortgagee, the failure of Lessee to pay any installment of Basic Rent within one Business Day after the same shall become due, if any portion of such installment was then required to be paid to the Mortgagee, which failure shall constitute knowledge of a Default) unless notified in writing by Lessee, the Owner Trustee, the Owner Participant or one or more Note Holders.

  • Status Substantial Compliance Analysis The Compliance Officer found that PPB is in substantial compliance with Paragraph 80. See Sections IV and VII Report, p. 17. COCL carefully outlines the steps PPB has taken—and we, too, have observed—to do so. Id. We agree with the Compliance Officer’s assessment. In 2018, the Training Division provided an extensive, separate analysis of data concerning ECIT training. See Evaluation Report: 2018 Enhanced Crisis Intervention Training, Training usefulness, on-the-job applications, and reinforcing training objectives, February 2019. The Training Division assessed survey data showing broad officer support for the 2018 ECIT training. The survey data also showed a dramatic increase in the proportion of officers who strongly agree that their supervisors are very supportive of the ECIT program, reaching 64.3% in 2018, compared to only 14.3% in 2015: The Training Division analyzed the survey results of the police vehicle operator training and supervisory in-service training, as well. These analyses were helpful in understanding attendees’ impressions of training and its application to their jobs, though the analyses did not reach as far as the ECIT’s analysis of post-training on- the-job assessment. In all three training analyses, Training Division applied a feedback model to shape future training. This feedback loop was the intended purpose of Paragraph 80. PPB’s utilization of feedback shows PPB’s internalization of the remedy. We reviewed surveys of Advanced Academy attendees, as well. Attendees were overwhelmingly positive in response to the content of most classes. Though most respondents agreed on the positive aspects of keeping the selected course in the curriculum, a handful of attendees chose options like “redundant” and “slightly disagree,” indicating that the survey tools could be used for critical assessment and not merely PPB self-validation. We directly observed PPB training and evaluations since our last report. PPB provided training materials to the Compliance Officer and DOJ in advance of training. Where either identified issues, PPB worked through those issues and honed its materials. As Paragraph 80 requires, PPB’s training included competency-based evaluations, namely: knowledge checks (i.e., quizzes on directives), in-class responsive quizzes (using clickers to respond to questions presented to the group); knowledge tests (examinations via links PPB sent to each student’s Bureau-issued iPhone); demonstrated skills and oral examination (officers had to show proficiency in first aid skills, weapons use, and defensive tactics); and scenario evaluations (officers had to explain their reasoning for choices after acting through scenarios). These were the same sort of competency-based evaluations we commended in our last report. In this monitoring period, PPB applied the same type of evaluations to supervisory-level training as well as in-service training for all sworn members. PPB successfully has used the surveys, testing, and the training audit.

  • Termination on Material Default 30.2.1 The Authority may terminate this Framework Agreement for material Default by issuing a Termination Notice to the Supplier where:

  • Notification of Delay The Design Professional shall immediately notify the City in writing if Design Professional experiences or anticipates experiencing a delay in performing the Professional Services within the time frames set forth in the Task Order. The written notice shall include an explanation of the cause for, and a reasonable estimate of the length of, the delay. If in the opinion of the City, the delay affects a material part of the Task, the City may exercise its rights under Sections 2.5-2.7 of this Agreement.

  • Actions in Event of Breach Upon Contractor’s material breach, the Department may:  terminate this contract under Section 17.1 and pursue any of its remedies under this contract, at law, or in equity; or  treat this contract as materially breached and pursue any of its remedies under this contract, at law, or in equity. Upon the Department’s material breach, Contractor may:  terminate this contract under Section 17.2 and pursue any of its remedies under this contract, at law, or in equity; or  treat this contract as materially breached and, except as the remedy is limited in this contract, pursue any of its remedies under this contract, at law, or in equity.

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

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