Incident and Root Cause Analysis Reporting Sample Clauses

Incident and Root Cause Analysis Reporting. Within 3 days of a Severity Level 1 Incident, Contractor will provide a Root Cause Analysis and details of steps that will be taken in order to prevent a reoccurrence of similar issues for all Severity Level 1 Incidents. As soon as reasonably possible following the occurrence of a Severity Level 1 Incident, a Critical Incident Report (the “CIR”) will be provided containing a description of the Incident, date and timestamp, outage duration, root cause of incident, resolution/recovery actions taken and steps that will be taken to prevent a reoccurrence of similar issues.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs

Related to Incident and Root Cause Analysis Reporting

  • Incident Reporting Transfer Agent will use commercially reasonable efforts to promptly furnish to Fund information that Transfer Agent has regarding the general circumstances and extent of such unauthorized access to the Fund Data.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11165.7, AB 1432, and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.

  • Management Reporting (a) Provide periodic reports, in accordance with agreed upon frequency and content parameters, to the Funds. As reasonably requested by the Funds, the Transfer Agent shall furnish ad hoc reports to the Funds.

  • Loop Testing/Trouble Reporting 2.1.6.1 TeleConex will be responsible for testing and isolating troubles on the Loops. TeleConex must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, TeleConex will be required to provide the results of the TeleConex test which indicate a problem on the BellSouth provided Loop.

  • Accident Reporting 25.1 If You or an Authorised Driver has an Accident or if the Vehicle is stolen You must report the Accident or theft to Us within 24 hours of it occurring and fully complete an Accident/Theft report form.

  • Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.

  • Additional Reporting 37. Within seven days after the date of this Agreement, the Recipient shall register in XXX.xxx, and thereafter maintain the currency of the information in XXX.xxx until at least October 1, 2022. The Recipient shall review and update such information at least annually after the initial registration, and more frequently if required by changes in the Recipient’s information. The Recipient agrees that this Agreement and information related thereto, including the Maximum Awardable Amount and any executive total compensation reported pursuant to paragraph 38, may be made available to the public through a U.S. Government website, including XXX.xxx.

  • Sick Leave Reporting and Verification Employees must promptly notify their supervisor on their first day of sick leave and each day after, unless there is mutual agreement to do otherwise. If an employee is in a position where a relief replacement is necessary if they are absent, they will notify their supervisor at least two (2) hours prior to their scheduled time to report to work (excluding leave taken in accordance with the Domestic Violence Act). Unless otherwise precluded by law, the Employer has reason to suspect abuse, the Employer may require a written medical certificate for any sick leave absence. An employee returning to work after any sick leave absence may be required to provide written certification from their health care provider that the employee is able to return to work and perform the essential functions of the job with or without reasonable accommodation.

  • PERFORMANCE MONITORING AND REPORTING Performance indicators

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