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. Correction 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.
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.
Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.
Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.
Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.
Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.
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.
Change in Effective Control A Change in Effective Control occurs if, over a twelve (12) month period: (i) a person or group acquires stock representing thirty percent (30%) of the voting power of the corporation; or (ii) a majority of the members of the board of directors of the ultimate parent corporation is replaced by directors not endorsed by the persons who were members of the board before the new directors’ appointment, as defined in Treasury Regulations §1.409A-3(i)(5)(vi).
Change in Ownership Any change in ownership of twenty-five percent (25%) or more of the common stock of Borrower.
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.
