All Incidents Sample Clauses

All Incidents. Service Provider’s responsibilities include: 1. Receive and record all Incidents (including submissions received by telephone, electronically, or other means approved by DIR) in an Incident Record or Service Request Record as appropriate, including classification and initial support. 2. Enable Incident detection by DCS Service Providers (including links to event monitoring tools), reporting, recording, classification and initial support. 3. Provide Incident investigation, diagnosis, impact analysis, and reclassification as required. 4. Utilize and update the Incident Management System with all relevant information relating to an Incident within the designated time and in a complete manner. 5. Make an initial determination of the potential Resolution and document in the Incident Management System. 6. Resolve Incidents requiring Level 1 Support and close after receiving confirmation to close from the affected Authorized User, or Service Provider support personnel for Incidents reported via an event detection tool. 7. Ensure resolution of Incidents arising from or related to the Services, including break/fix Hardware and Software support. 8. Act proactively, and coordinate with all other third parties to Resolve Incidents and action Service Requests in a way that ensures effective coordination and avoids conflict of resource allocations, control objectives, etc. 9. Transfer Incidents within specified time limits to the appropriate party without compromising Service Levels or security requirements. 10. Ensure that proper escalation and prioritization policies and procedures are properly managed to ensure that incident response and resolution is handled within the intents and guidelines of the prioritization model agreed to. 11. Provide or coordinate the final Resolution including Service Request Management. 12. Ensure proper testing of incident resolution responses to ensure effective resolution and closure of the incident while avoiding / minimizing (unintended) impact to the customer / user. 13. Escalate issues to the appropriate levels/functions for Resolution in accordance with escalation procedures approved by DIR. 14. Escalate an Incident where the Incident cannot be Resolved within the relevant Service Levels or agreed timeframe. 15. Ensure consistent ownership of the Incident from recording to Resolution. 16. Record all information on the details of the Incident and the corrective action for later statistical analysis. 17. Create an audit trail of all ...
View SourceView Similar (5)

Related to All Incidents

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

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

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

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

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