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 ...
AutoNDA by SimpleDocs

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.

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

  • PROCEDURE FOR DEALING WITH SAFETY ISSUES OR INCIDENTS 11.1 The Employer, the Employees and the Union agree that for the purposes of s. 81 of the WHS Act matters about work health and safety arising at the workplace shall be resolved in accordance with this procedure. 11.2 The Parties agree that for the purposes of this procedure and s. 81(3) of the WHS Act the following persons shall be the representatives of the following parties: (a) the Principal Contractor (as defined in the WHS Act) - Site Manager or any other person nominated by the Principal Contractor (b) the Employers - the Site Manager or any other person nominated by the Employer(s) (c) The Employees - the Union or other representatives. (Collectively referred to as "Nominated Parties”) 11.3 The Nominated Parties agree that representatives shall be entitled to: (a) inspect any work system, plant, substance, structure, or other thing relevant to resolving the issue (b) consult with relevant Employees in relation to resolving the issue (c) consult with the relevant PCBU (as defined in the WHS Act) about resolving the issue (d) inspect and take copies of any document that is directly relevant to resolving the issue; and (e) advise any person whom the representative reasonably believes to be exposed to a serious risk to his or her health and safety, emanating from an immediate and imminent exposure to a hazard of that risk. 11.4 The Nominated Parties and/or their representatives may commence the procedure by informing, either by themselves or their representative, the other Parties and/or representatives that: (a) there is an issue to be resolved; and (b) the nature and scope of the issue. 11.5 As soon as the Parties and/or their representatives are informed of the issue, the Nominated Parties and/or their representatives must meet or communicate with each other to attempt to resolve the issue. 11.6 The Nominated Parties and/or their representatives must have regard to all relevant matters including: (a) the degree and imminent risk to the Employees or other persons affected by the issue. (b) the number and location of Employees and other persons affected by the issue. (c) the measures both temporary and permanent that must be implemented to resolve the issue. (d) who will be responsible for implementing the resolution measures. (e) whether the hazard or risk can be isolated; and (f) the time that may elapse before the hazard or risk is permanently corrected. 11.7 Once the issue is resolved details of the issue and its resolution must be set out in writing with all Nominated Parties and/or their representatives to be satisfied that the agreement reflects the resolution of the issue with a copy given to all Nominated Parties and/or their representatives to the issue. The issue, once resolved, shall be recorded in the next safety committee meeting minutes with the agreed resolution. 11.8 The Nominated Parties and/or their representatives must make reasonable efforts to achieve a timely and final resolution of the issue. If within a reasonable time there is still no resolution, any of the Nominated Parties attempting to resolve the issue may then ask Work Health and Safety Queensland, and/or the QBCC, where applicable, to arrange for an inspector to attend the workplace to assist in resolving the issue. 11.9 Direction to cease work (a) If - (i) an issue concerning health or safety arises at a workplace or from the conduct of the undertaking of the Employer; and (ii) the issue concerns work which involves an immediate threat to the health or safety of any person; and (iii) given the nature of the threat and degree of risk, it is not appropriate to adopt the processes set out in clause 11.7 above (b) the Employer and/or the health and safety representative for the designated work group in relation to which the issue has arisen may, after consultation between them, direct that the work is to cease. (c) During any period for which work has ceased in accordance with such a direction, the Employer may assign any Employees whose work is affected to suitable and safe alternative work. 11.10 Fundamental to this process is a standing invitation for Union representatives to attend site to assist with all matters relating to health and safety. 11.11 Employees are not required to work in circumstances where the employee or a Union representative reasonably believes a safety law is being, or will be, contravened. Consultation between the relevant parties will occur throughout this procedure including with senior representatives of the Employer and the Union.

  • 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 Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Causes The contract may be terminated before the stated completion date by any of the following conditions. 1. By mutual agreement and consent, in writing from both parties. 2. By the State by notice in writing to the Engineer as a consequence of failure by the Engineer to perform the services set forth herein in a satisfactory manner. 3. By either party, upon the failure of the other party to fulfill its obligations as set forth herein. 4. By the State for reasons of its own, not subject to the mutual consent of the Engineer, by giving thirty business days notice of termination in writing to the Engineer. 5. By the State, if the Engineer violates the provisions of Attachment A, General Provisions Article 21, Gratuities, or Attachment H, Disadvantaged Business Enterprise/Historically Underutilized Business Requirements. 6. By satisfactory completion of all services and obligations described herein.

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