Severity 3 Clause Samples
The 'Severity 3' clause defines a specific level of issue or incident, typically indicating a moderate or non-critical problem that affects the use of a product or service but does not prevent its basic operation. In practice, this classification is used to prioritize support responses, where Severity 3 issues might include minor bugs, limited functionality loss, or inconveniences that do not halt business processes. By clearly categorizing the seriousness of issues, the clause helps manage expectations for response times and resource allocation, ensuring that more critical problems are addressed first while still providing a framework for resolving less urgent matters.
Severity 3. Severity 3 Defects will be addressed in Alchemy’s normal maintenance or enhancement release schedule.
Severity 3. A Non-Critical Function cannot be completed by the specified process, inflicting significant nuisance upon the Authority or; one or more Non-Critical Functions have significantly reduced performance, taking longer than expected to be completed.
Severity 3. A Severity 3 incident is characterized as a minor degradation of the Services which is isolated to non-essential features specified in the Agreement, specifications and/or any applicable statement of work attached thereto; Severity 3 incidents are generally non-service affecting conditions under which the service is usable but with limited functionality. The condition is not critical to overall operations, and does not severely restrict such operations. Mercury – Confidential & Proprietary This incident level is characterized by the following conditions: • Low business impact • Failures that have minor system impact • Non-service impacting intermittent system faults • Web interface defects that have little or no impact on a Mercury’s ability to utilize Services features and functions
Severity 3. The system or application is moderately affected. The issue is not critical and the system has not failed. The issue has been identified and does not hinder normal operation, or the situation may be temporarily circumvented using an available workaround. The Company will work during normal business hours to provide reasonable effort for workaround or solution within 10 business days, once the issue is reproducible.
Severity 3. Severity 3 Defects will be addressed in ElementLMS’s normal maintenance or enhancement release schedule.
Severity 3. A problem that negatively affects the usability of the system but does not prevent access to the system or completion of standard business processes, an incorrectly functioning application feature is preventing the completion of a non-critical business process.
Severity 3. The lowest level Trouble Ticket in this SLA; Severity 3 Trouble Tickets include bugs or non-conformities where a workaround is possible and other issues that do not require immediate response. Changes to End-User preferences and general questions about the Services are not covered under this SLA.
Severity 3. An Error that does not materially affect the overall performance of a production function or process. This may include a minor issue with limited loss or no loss of functionality or impact to Customer's operations.