Occurrence of Incidents Sample Clauses

Occurrence of Incidents. District shall timely notify University when any University employee or student has been involved in a reported incident and University shall have the opportunity to participate in any ongoing investigation and shall have access to any oral or written reports and any other documentation related to the reported incident. University shall cooperate in any investigation of a potential liability inducing incident.
AutoNDA by SimpleDocs

Related to Occurrence of Incidents

  • Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.

  • Relief Events Subject to Clause 13.3, and notwithstanding any other provision of this Agreement, the Supplier shall have no liability for failure to perform the Services or its other obligations under this Agreement if it is prevented, hindered or delayed in doing so as a result of any Relief Event.

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

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

  • EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE BNPP ENTITIES OR THEIR SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR PERSONAL INJURY, FOR LOSS OF PRIVACY, FOR FAILURE TO MEET ANY DUTY INCLUDING OF GOOD FAITH OR OF REASONABLE CARE, FOR NEGLIGENCE, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT SERVICES, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS SECTION 19, EVEN IN THE EVENT OF THE FAULT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, BREACH OF CONTRACT OR BREACH OF WARRANTY OF THE BNPP ENTITIES OR ANY SUPPLIER, AND EVEN IF THE BNPP ENTITIES OR ANY SUPPLIER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL ANY BNPP ENTITY OR ANY SUPPLIER BE LIABLE FOR ACTS OF GOD, ACTS OF WAR OR TERRORISM, MACHINE OR COMPUTER BREAKDOWN OR MALFUNCTION, INTERRUPTION OR MALFUNCTION OF COMMUNICATION FACILITIES, LABOR DIFFICULTIES OR ANY OTHER SIMILAR OR DISSIMILAR CAUSE BEYOND THEIR REASONABLE CONTROL.

  • Data Incidents Merchant must report all instances of a Data Incident (as defined in the American Express Merchant Operating Guide) immediately to ISO after discovery of the incident. Merchant must ensure data quality and that Transaction Data and customer information is processed promptly, accurately, and completely, and complies with the American Express Technical Specifications. THE FOLLOWING SERVICES ARE PROVIDED BY ISO ONLY. Bank shall not have any obligation or liability of any nature in connection with such services. PART THREE

  • Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”):

  • Consequences of an Event of Default (a) If an Event of Default specified in subsections (a) through (l), (o), (p) or (q) of Section 7.01 shall occur and, be continuing or shall exist, then, in addition to all other rights and remedies which the Administrative Agent or any Lender may have hereunder or under any other Loan Document, at law, in equity or otherwise, the Lenders shall be under no further obligation to make Loans hereunder, and the Administrative Agent may, and, upon the written request of the Required Lenders shall, by notice to the Borrower, from time to time do any or all of the following:

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