Incident Reporting Procedure. In order to report an Incident, the Customer shall complete the form designed for such purpose on the website, then go to the Customer’s Management Interface where earlier tickets of electronic exchanges between the Customer and OVH may be found. The Customer shall complete the form on he OVH Site and attempt to provide as much information as possible on the problem encountered to help with the Diagnostic. To this end, the Customer explicitly authorizes OVH and its staff to connect to the Customer’s Service and to perform any operation required in connection with the Diagnostic, with respect to both the hardware and the software. OVH reserves the right to reject any intervention in this regard if OVH notices in its research work that the Customer uses the Service in breach of OVH’s General and Specific Terms and Conditions or of laws and regulations in force. All the exchanges between the parties, and more particularly the electronic exchanges and telephone conversations, shall reflect Customer’s assent to OVH’s intervention.
Incident Reporting Procedure. 2.1 If a Customer experiences an Incident, the Customer must take all reasonable steps to ensure that the Incident is not a fault within the Customer’s Responsibility Domain before reporting the Incident to Interactive.
2.2 If the Customer is satisfied that the Incident is not due to an issue within its Responsibility Domain, the Customer may report the Incident to Interactive's Service Desk as follows: Phone: 0000 000 000 (in Australia) or +00 0 0000 0000 (internationally) Online: xxxx://xxx.xxxxxxxxxxx.xxx.xx/xxxxxxx Email: xxxxxxx@xxxxxxxxxxx.xxx.xx
2.3 When reporting an Incident, Customers must provide the following information to Interactive:
(a) Customer Name and service(s) affected by the Incident.
(b) Description of the Incident, including the Customer’s classification of the urgency and impact of the Incident in accordance with Table 1 and Table 2.
(c) Name and contact details of the person reporting the Incident.
(d) Name and location of the site affected by the Incident.
(e) Business / trading hours of the site affected by the Incident.
2.4 The Service Desk provides a 24 x 7 x 365 service for severity 1 and 2 Incidents and Business Hours for other Incidents and Service Requests.
2.5 Severity 1 and Severity 2 Incidents must be logged by telephone only. Severity 1 and Severity 2 Incidents not logged by telephone are exempt from the calculation of Service Levels. Severity 3 and Severity 4 Incidents may be logged by telephone or email.
2.6 Interactive, at its sole discretion, may charge the Customer a reasonable amount, based on the Standard Charge Out Rate, to diagnose an Incident if the Customer knew, ought to have known, or would have known following reasonable investigation, that the Incident was not caused by Interactive, or was caused by something within the Customer’s Responsibility Domain.
Incident Reporting Procedure. (a) If the Customer experiences an Incident, the Customer must take reasonable steps to ensure that the Incident is not within the Customer’s Responsibility Domain before reporting the Incident to Interactive.
(b) If, after taking those steps, the Customer is satisfied that an Incident is within the Customer’s Responsibility Domain, the Customer may report the Incident to the Interactive Service Desk in accordance with the procedure set out in clause 9
(c) When logging an Incident Call, the Customer must provide the following information:
(i) Customer Name and Service ID affected by the Incident.
(ii) Description of the Incident.
(iii) Name and contact details of the person reporting the Incident.
(iv) Name and address of the Customer Location.
(v) Business / trading hours of the Customer Location.
(d) Interactive will issue all Incidents logged with the Service Desk with an Incident number. This Incident number will be the sole reference number for the Incident and will be referenced in subsequent communication from Interactive regarding the Incident.
(e) The Customer may log non-critical issues that do not affect the Service, but do require attention, by phone call or emailing the Service Desk. Interactive will provide an Incident number for all issues, including non-critical issues. Interactive will respond by email to all Incidents the Customer logs by email.
(f) Interactive, may acting reasonably charge the Customer a reasonable amount, based on the Standard Charge Out Rate, to diagnose an Incident if the Customer knew, ought to have known, or would have known following reasonable investigation, that the Incident was not caused by Interactive, or was caused by something within the Customer’s Responsibility Domain.
Incident Reporting Procedure. REQUIREMENTS The provider agrees to comply with the Department of Juvenile Justice, Inspector General's Statewide Incident Reporting Procedure. Failure to comply with this procedure could result in cancellation of the contract.
Incident Reporting Procedure. 0.0.0. Xx order to report an Incident, the Customer shall complete the Incident Reporting Form designed for such purpose on the website, then go to the Customer’s Management Interface where earlier tickets of electronic exchanges between the Customer and OVH may be found.
5.2.2. The Customer shall complete the Incident Reporting Form and attempt to provide as much information as possible on the problem encountered to help with the Diagnostic.
0.0.0. Xx filing an Incident Reporting Form, the Customer acknowledges and agrees that he/it expressly authorizes OVH and its staff to connect to the Customer’s Services and to perform any operation required in connection with the Diagnostic, with respect to both the hardware and the software. OVH reserves the right to reject any intervention in this regard if OVH notices in its research work that the Customer uses the Services in breach of OVH’s General and Specific Terms and Conditions or of laws and regulations in force.
5.2.4. Therefore, OVH cannot be held liable for its intervention following the lodging by the Customer of an Incident Reporting Form.
Incident Reporting Procedure. 6.6.1 On observing an incident, one shall immediately activate an alerting process as follows: i). Inform supervisor by Radio or Telephone
Incident Reporting Procedure. In order to report an Incident, the Customer shall complete the form designed for such purpose on the website, then go to the Customer’s Client Area where earlier tickets of electronic exchanges between the Customer and Nuagerie may be found. The Customer shall complete the form on the Nuagerie Site and attempt to provide as much information as possible on the problem encountered to help with the Diagnostic. To this end, the Customer explicitly authorizes Nuagerie and its staff to connect to the Customer’s Service and to perform any operation required in connection with the Diagnostic, with respect to both the hardware and the software. Nuagerie reserves the right to reject any intervention in this regard if Nuagerie notices in its research work that the Customer uses the Service in breach of Nuagerie’s General and Specific Terms and Conditions or of laws and regulations in force. All the exchanges between the parties, and more particularly the electronic exchanges and telephone conversations, shall reflect Customer’s assent to Nuagerie’s intervention.
Incident Reporting Procedure. In order to report an Incident, the Customer shall complete the form designed for such purpose on the website, then go to the Customer’s Management Interface where earlier tickets of electronic exchanges between the Customer and Divvy Hosting may be found. The Customer shall complete the form on the Divvy Hosting Site and attempt to provide as much information as possible on the problem encountered to help with the Diagnostic. To this end, the Customer explicitly authorizes Divvy Hosting and its staff to connect to the Customer’s Service and to perform any operation required in connection with the Diagnostic, with respect to both the hardware and the software. Divvy Hosting reserves the right to reject any intervention in this regard if Xxxxx Hosting notices in its research work that the Customer uses the Service in breach of Divvy Hosting’s General and Specific Terms and Conditions or of laws and regulations in force. All the exchanges between the parties, and more particularly the electronic exchanges and telephone conversations, shall reflect Customer’s assent to Divvy Hosting’s intervention
Incident Reporting Procedure. In order to report an Incident, the Customer shall complete the form designed for such purpose on the website, then go to the Customer’s Management Interface where earlier tickets of electronic exchanges between the Customer and Lanka Web Hosting may be found. The Customer shall complete the form on the Lanka Web Hosting Site and attempt to provide as much information as possible on the problem encountered to help with the Diagnostic. To this end, the Customer explicitly authorizes Lanka Web Hosting and its staff to connect to the Customer’s Service and to perform any operation required in connection with the Diagnostic, with respect to both the hardware and the software. Lanka Web Hosting reserves the right to reject any intervention in this regard if Lanka Web Hosting notices in its research work that the Customer uses the Service in breach of Lanka Web Hosting’s General and Specific Terms and Conditions or of laws and regulations in force. All the exchanges between the parties, and more particularly the electronic exchanges and telephone conversations, shall reflect Customer’s assent to Lanka Web Hosting’s intervention
Incident Reporting Procedure. In order to report an Incident, the Customer shall complete the form designed for such purpose on the website, then go to the Customer’s Management Interface where earlier tickets of electronic exchanges between the Customer and NEXUS may be found. The Customer shall complete the form on the NEXUS Site and attempt to provide as much information as possible on the problem encountered to help with the Diagnostic. To this end, the Customer explicitly authorizes NEXUS and its staff to connect to the Customer’s Service and to perform any operation required in connection with the Diagnostic, with respect to both the hardware and the software. NEXUS reserves the right to reject any intervention in this regard if NEXUS notices in its research work that the Customer uses the Service in breach of NEXUS’ General and Specific Terms and Conditions or of laws and regulations in force. All the exchanges between the parties, and more particularly the electronic exchanges and telephone conversations, shall reflect Customer’s assent to NEXUS’ intervention.
