Breach Incidents Sample Clauses

Breach Incidents. Upon becoming aware of a Breach Incident, Company will notify Customer without undue delay and will provide information relating to the Breach Incident as reasonably requested by Customer. Company will use reasonable endeavors to assist Customer in mitigating, where possible, the adverse effects of any Breach Incident.
AutoNDA by SimpleDocs
Breach Incidents. Upon becoming aware of a Breach Incident, Company will notify Developer without undue delay and will provide information relating to the Breach Incident as reasonably requested by Developer . Company will use reasonable endeavors to assist Developer in mitigating, where possible, the adverse effects of any Breach Incident.
Breach Incidents. We will notify Customer of security breach incidents involving Customer’s information as required by and in accordance with Applicable Law. security and confidentiality of the Security Procedures, and (b) institute and use prudent
Breach Incidents. 9.1. No later than 30 days from the discovery of the Breach after becoming aware thereof, AllCloud will notify Customer and will provide information known to it at such time with respect to the nature, scope and consequences of such Breach Incident. 9.2. AllCloud will use reasonable endeavors to assist Customer in mitigating, where possible, the adverse effects of any Breach Incident. 9.3. AllCloud’s obligations under this Section shall not apply to Breach Incidents that are caused by Customer. 9.4. Taking into account the scope and nature of the services, Upon reasonable notice, AllCloud shall provide reasonable assistance to Customer in compliance with any notification obligations of Breach Incidents to the supervisory as required under the Applicable Data Protection Laws.

Related to Breach Incidents

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

  • No Conflict, Breach, Violation or Default The execution, delivery and performance of the Transaction Documents by the Company and the issuance and sale of the Securities will not conflict with or result in a breach or violation of any of the terms and provisions of, or constitute a default under (i) the Company’s Articles of Incorporation or the Company’s Bylaws, both as in effect on the date hereof (true and complete copies of which have been made available to the Investor through the XXXXX system), or (ii)(a) any statute, rule, regulation or order of any governmental agency or body or any court, domestic or foreign, having jurisdiction over the Company, any Subsidiary or any of their respective assets or properties, or (b) any agreement or instrument to which the Company or any Subsidiary is a party or by which the Company or a Subsidiary is bound or to which any of their respective assets or properties is subject.

  • Breach Waiver Any waiver by the Client of a breach of any section of this Agreement by the Contractor shall not operate or be construed as a waiver of any subsequent breach by the Contractor.

  • Breach of Contract Claims [Option (Include if University prefers an abbreviated Breach of Contract Claims provision): To the extent that Chapter 2260, Texas Government Code, is applicable to this Agreement and is not preempted by other applicable law, the dispute resolution process provided for in Chapter 2260 and the related rules adopted by the Texas Attorney General pursuant to Chapter 2260, will be used by University and Contractor to attempt to resolve any claim for breach of contract made by Contractor that cannot be resolved in the ordinary course of business. The chief business officer of University will examine Contractor's claim and any counterclaim and negotiate with Contractor in an effort to resolve the claims. The parties specifically agree (i) neither execution of this Agreement by University nor any other conduct, action or inaction of any representative of University relating to this Agreement constitutes or is intended to constitute a waiver of University’s or the state's sovereign immunity to suit; and (ii) University has not waived its right to seek redress in the courts.] 19.1 To the extent that Chapter 2260, Texas Government Code, as it may be amended from time to time (Chapter 2260), is applicable to this Agreement and is not preempted by other Applicable Laws, the dispute resolution process provided for in Chapter 2260 will be used, as further described herein, by University and Contractor to attempt to resolve any claim for breach of contract made by Contractor: 12.19.1.1 Contractor’s claims for breach of this Agreement that the parties cannot resolve pursuant to other provisions of this Agreement or in the ordinary course of business will be submitted to the negotiation process provided in subchapter B of Chapter 2260. To initiate the process, Contractor will submit written notice, as required by subchapter B of Chapter 2260, to University in accordance with the notice provisions in this Agreement. Contractor's notice will specifically state that the provisions of subchapter B of Chapter 2260 are being invoked, the date and nature of the event giving rise to the claim, the specific contract provision that University allegedly breached, the amount of damages Contractor seeks, and the method used to calculate the damages. Compliance by Contractor with subchapter B of Chapter 2260 is a required prerequisite to Contractor's filing of a contested case proceeding under subchapter C of Chapter 2260. The chief business officer of University, or another officer of University as may be designated from time to time by University by written notice to Contractor in accordance with the notice provisions in this Agreement, will examine Contractor's claim and any counterclaim and negotiate with Contractor in an effort to resolve the claims. 12.19.1.2 If the parties are unable to resolve their disputes under Section 12.19.1.1, the contested case process provided in subchapter C of Chapter 2260 is Contractor’s sole and exclusive process for seeking a remedy for any and all of Contractor's claims for breach of this Agreement by University. 12.19.1.3 Compliance with the contested case process provided in subchapter C of Chapter 2260 is a required prerequisite to seeking consent to xxx from the Legislature under Chapter 107,

  • Material Breach of Contract In the event Contractor fails to deliver the product and services as contracted for herein, to the satisfaction of the City of Sparks or otherwise fails to perform any provisions of this Contract, the City, after providing five (5) days written notice and Contractor’s failure to cure such breach within the time specified in the notice, may without waiving any other remedy, make good the deficiencies and deduct the actual cost of providing alternative products and/or services from payment due the Contractor. Non-performance after the first notice of non-performance shall be considered a material breach of contract.

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

  • Data Breaches 4.1 The Data Processor does not guarantee that its security measures will be effective under all conditions. If the Data Processor discovers a data breach within the meaning of Article

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • BREACH; TERMINATION Customer/Project Sponsor may terminate this Agreement at any time in its sole discretion by providing notice to the Company not less than one hundred and eighty (180) days before such termination. In the event of breach of any material terms or conditions of this Agreement, if the breach has not been remedied within 30 days following receipt of written notice thereof from the other Party (provided that, if the breaching Party has commenced and is diligently pursuing efforts to cure such breach, then such 30-day period shall be extended until the earlier of (i) 30 additional days or (ii) end of diligent efforts to cure the breach), then the non-breaching party may terminate this Agreement by written notice at any time until cure of such breach occurs. In the event of any proceedings by or against either Party in bankruptcy, insolvency or for appointment of any receiver or trustee or any general assignment for the benefit of creditors (excluding, for the avoidance of doubt, an assignment in accordance with Article XI or other collateral assignment to obtain project financing), the other Party may terminate this Agreement. If the Customer/Project Sponsor increases the capability or the capacity of the Facility to exceed 4.999 MW, this Agreement shall immediately terminate. The Company shall not be liable to the Customer/Project Sponsor for damages resulting from a termination pursuant to this paragraph. If the Customer/Project Sponsor's generating equipment produces zero (0) kilowatt- hours during any period of twelve (12) consecutive Billing Periods after the Commercial Operation Date [Effective Date for existing resources] for a reason other than a force majeure event, the Company may terminate this Agreement.

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