Severity Level. Two (2) This is defined as a failure that results in diminished user access of the system. The following are examples of this kind of failure:
Severity Level. Two (2) This is defined as a failure that results in diminished user access of the system. The following are examples of this kind of failure: • Failure of any complete Alarm portions/area Response Time: The Contractor will respond within Twelve hours (12hr) of the initial service call for support being received by the Contractor. Standby back-up services to be on site within 5minutes of reported failure and camp until system restoration.
Severity Level. Two (2) This is defined as a failure that results in diminished user access of the system. The following are examples of this kind of failure: • Lack of clarity in cameras, monitors etc. • Failure of one or two cameras which have complementary coverage from other cameras. • Failure of any complete sub-system/section which does not affect more than 50% of the system. Response Time: The Contractor will respond within Twelve hours (12hr) of the initial service call for support being received by the Contractor.
Severity Level. The level of bugs/Issue/Incident that prevent the Software for doing what is supposed to do.
Severity Level. 8.1 Upon receipt of a properly submitted Ticket, the Supplier shall agree the Incident Severity Level jointly with the Client according to the guidelines defined below. Severity Level may be re-evaluated upon submission of a Workaround. Severity Level 1 is defined as a critical problem that impacts the Client’s ability to deliver the Software or the services that the Software enables. the Client’s critical production systems experience a total loss of the service provided or enabled by the Software. Severity Level 2 is defined as a major problem that impacts the Client’s ability to deliver the Software or the services that the Software enables. the Client’s business production systems experience significant loss or degradation of the service provided or enabled by the Software. Severity Level 3 is defined as a minor problem that does not impact the Client’s ability to deliver the Software or the services that the Software enables. the Client’s business production systems do not experience any loss or degradation of the service provided or enabled by the Software. Severity Level 4 is defined as all other problems related to the Software or the services that the Software enables. Table 1: Severity Levels
Severity Level. The LICENSEE is required to provide the severity level of the help ticket request.
Severity Level. In order to establish the common understanding of the criticality of the fault / problems / bugs and to enable Argoid and the User to take action accordingly, the same are defined here below which shall be the base for categorizing the nature of faults / problems / bugs.
Severity Level. 2 An Incident or Problem is considered a Severity Level 2 or High Priority if the Incident or Problem is characterized by the following:
Severity Level. 3 An Incident or Problem is considered a Severity Level 3 or Medium Priority if the Incident or Problem is characterized by the following:
Severity Level. The following severity levels shall be assigned in accordance with this Section 8 to support requests and Customer shall be able to view and comment on these using the online support website:
