How to Report an Incident Sample Clauses

How to Report an Incident. In order to expedite the resolution of Incidents, NT expects that Customer will make every attempt possible to:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
How to Report an Incident. In order to accelerate the resolution of Incidents, SPARKnit expects that Customer will make every attempt possible to: 1. Provide information necessary to help SPARKnit track, prioritize, reproduce, or investigate the Incident. 2. Provide a detailed description of the issue and expected results. 3. Categorize issues (technical question, defect, license request, enhancement request, etc.). 4. Provide SPARKnit with all data that is relevant issue that help SPARKnit investigate and resolve the issue. Relevant data may include, but is not limited to, log files, screenshots, database dumps, program scripts, descriptions of the hardware and software environment, examples of inputs, and expected and actual outputs. 5. Provide exact wording of all issue-related error messages. 6. Describe any special circumstances surrounding the discovery of the issue, e.g., first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem on Customer, and suggested urgency.
Sample 1Sample 2
How to Report an Incident. In order to expedite the resolution of Incidents, CFEngine expects that Customer will make every attempt possible to: a. Verify that the Incident is reproducible on the Supported Platforms for the Software (as applicable). b. Provide information necessary to help CFEngine track, prioritize, reproduce or investigate the Incident, such as: Customer name and organization. c. A full description of the issue and expected results. d. Category of issues: general question, defect, enhancement request, etc. e. Steps to reproduce the issue and relevant data. f. Any applicable log files or console output. g. Exact wording of all issue related error messages. h. Any special circumstances surrounding the discovery of the issue, i.e. first occurrence or occurred after what specific event, Customer’s business impact of problem and suggested priority for resolution. i. Identifying issue number in any ongoing communications with CFEngine on an existing issue.
Sample 1
How to Report an Incident. In order to expedite the resolution of Incidents, Nintex expects that Customer will make every attempt possible to: a. Verify that the Incident is reproducible (as applicable). b. Provide information necessary to help Nintex track, prioritize, reproduce, or investigate the Incident. c. Provide a full description of the issue and expected results. d. Categorize issues (technical question, defect, license request, enhancement request, etc.). e. List steps to reproduce the issue and relevant data. f. Provide any applicable log files (de-identified of sensitive data if appropriate). g. Provide exact wording of all issue-related error messages. h. Describe any special circumstances surrounding the discovery of the issue, e.g., first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem on Customer, and suggested urgency. i. Identify any existing Incident number in ongoing communications with Nintex.
Sample 1

Related to How to Report an Incident

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

  • Failure to Report No compensation shall be granted for the total period of standby if the employee is unable to report for duty when required.

  • Duty to report Force Majeure Event 21.5.1 Upon occurrence of a Force Majeure Event, the Affected Party shall by notice report such occurrence to the other Party forthwith. Any notice pursuant hereto shall include full particulars of: (a) the nature and extent of each Force Majeure Event which is the subject of any claim for relief under this Article 21 with evidence in support thereof; (b) the estimated duration and the effect or probable effect which such Force Majeure Event is having or will have on the Affected Party’s performance of its obligations under this Agreement; (c) the measures which the Affected Party is taking or proposes to take for alleviating the impact of such Force Majeure Event; and (d) any other information relevant to the Affected Party’s claim. 21.5.2 The Affected Party shall not be entitled to any relief for or in respect of a Force Majeure Event unless it shall have notified the other Party of the occurrence of the Force Majeure Event as soon as reasonably practicable, and in any event no later than 10 (ten) days after the Affected Party knew, or ought reasonably to have known, of its occurrence, and shall have given particulars of the probable material effect that the Force Majeure Event is likely to have on the performance of its obligations under this Agreement. 21.5.3 For so long as the Affected Party continues to claim to be materially affected by such Force Majeure Event, it shall provide the other Party with regular (and not less than weekly) reports containing information as required by Clause 21.5.1, and such other information as the other Party may reasonably request the Affected Party to provide.

  • RESPONDING TO REQUESTS FOR INFORMATION To the extent authorized by the Participating Consumer(s) and to the extent such individual permission is required by law, the Competitive Supplier shall, during normal business hours (as set forth above), respond promptly and without charge therefore to reasonable requests of the Town for information or explanation regarding the matters covered by this ESA and the supply of electricity to Participating Consumers. Competitive Supplier agrees to designate a service representative or representatives (the “Service Contacts”) who shall be available for these purposes, and shall identify the office address and telephone number of such representative(s). Whenever necessary to comply with this Article 5.3, the Service Contacts shall call upon other employees or agents of the Competitive Supplier to obtain such information or explanation as may be reasonably requested. Nothing in this Article 5.3 shall be interpreted as limiting the obligation of the Competitive Supplier to respond to complaints or inquiries from Participating Consumers, or to comply with any regulation of the Department or AG regarding customer service.

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

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