Incident Reporting Process Plan Sample Clauses

Incident Reporting Process Plan. ‌ Within forty-five (45) calendar days of execution of this Agreement, the Contractor shall provide CALNET CMO with an Incident Reporting Process Plan describing how the user reports service issues and opens incident for the services provided by the Contractor. If the Contractor provides an online incident reporting tool then details should be included in the process plan. The Incident Reporting Process Plan should include: 1. How Customer reports an issue and opens an incident; 2. How Customer inquiries about status of service issue; 3. Toll free number for Customers to report issues 24x7x365, except for established maintenance windows; 4. How Contractor will provide each Customer department access to the complete incident; 5. Include major milestones, roles and responsibilities, deliverables, and commitment dates as negotiated between CALNET CMO and the Contractor; and, 6. How Contractors technical services will respond to requests within four (4) hours of notice.
View SourceView Similar (3)

Related to Incident Reporting Process Plan

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

  • Reporting Procedures Enter in the ▇▇▇ Entity Management area the information that ▇▇▇ requires about each proceeding described in paragraph 2 of this award term and condition. You do not need to submit the information a second time under assistance awards that you received if you already provided the information through ▇▇▇ because you were required to do so under Federal procurement contracts that you were awarded.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

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

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.