Common use of Software Error Severity Classifications Clause in Contracts

Software Error Severity Classifications. All Software Errors shall be classified by RSA as follows: Error Severity Definition Examples 1 (“S1”) Critical: Severe problem preventing Customer or workgroup from performing critical business functions ▪ Production System data corruption (data loss, data unavailable) ▪ Production System crash or hang ▪ Production Systems significantly impacted, such as severe performance degradation ▪ Production System and/or data is at high risk of potential loss or interruption ▪ Production System workaround is required immediately ▪ Time critical Production cutover impacted 2 (“S2”) High: Customer or workgroup able to perform job function, but performance of job function degraded or severely limited ▪ Production System adversely impacted ▪ Non-Production System data corruption (data loss, data unavailable) ▪ Non-Production System crash or hang ▪ Non-Production System and/or data is at high risk of potential loss or interruption ▪ Non-Production System workaround is required immediately ▪ Development system(s) is inoperative 3 (“S3”) Medium: Customer or workgroup performance of job function is largely unaffected ▪ Production or development system has encountered a non- critical problem or defect and/or questions have arisen on product use. 4 (“S4”) Request: Minimal system impact; includes feature requests and other non-critical questions ▪ No Customer business impact ▪ Requests for enhancements by Customer

Appears in 5 contracts

Samples: Securid® Maintenance Agreement, Securid® Maintenance Agreement, Securid® Maintenance Agreement

AutoNDA by SimpleDocs

Software Error Severity Classifications. All Software Errors shall be classified by RSA SecurID as follows: Error Severity Definition Examples 1 (“S1”) Critical: Severe problem preventing Customer or workgroup from performing critical business functions ▪ Production System data corruption (data loss, data unavailable) ▪ Production System crash or hang ▪ Production Systems significantly impacted, such as severe performance degradation ▪ Production System and/or data is at high risk of potential loss or interruption ▪ Production System workaround is required immediately ▪ Time critical Production cutover impacted 2 (“S2”) High: Customer or workgroup able to perform job function, but performance of job function degraded or severely limited ▪ Production System adversely impacted ▪ Non-Production System data corruption (data loss, data unavailable) ▪ Non-Production System crash or hang ▪ Non-Production System and/or data is at high risk of potential loss or interruption ▪ Non-Production System workaround is required immediately ▪ Development system(s) is inoperative 3 (“S3”) Medium: Customer or workgroup performance of job function is largely unaffected ▪ Production or development system has encountered a non- critical problem or defect and/or questions have arisen on product use. 4 (“S4”) Request: Minimal system impact; includes feature requests and other non-critical questions ▪ No Customer business impact ▪ Requests for enhancements by Customer

Appears in 1 contract

Samples: Maintenance Agreement for Securid Products

Software Error Severity Classifications. All Software Errors shall be classified by RSA Outseer as follows: Error Severity Definition Examples 1 (“S1”) Critical: Severe problem preventing Customer or workgroup from performing critical business functions ▪ Production System data corruption (data loss, data unavailable) ▪ Production System crash or hang ▪ Production Systems significantly impacted, such as severe performance degradation ▪ Production System and/or data is at high risk of potential loss or interruption ▪ Production System workaround is required immediately ▪ Time critical Production cutover impacted 2 (“S2”) High: Customer or workgroup able to perform job function, but performance of job function degraded or severely limited ▪ Production System adversely impacted ▪ Non-Production System data corruption (data loss, data unavailable) ▪ Non-Production System crash or hang ▪ Non-Production System and/or data is at high risk of potential loss or interruption ▪ Non-Production System workaround is required immediately ▪ Development system(s) is inoperative 3 (“S3”) Medium: Customer or workgroup performance of job function is largely unaffected ▪ Production or development system has encountered a non- critical problem or defect and/or questions have arisen on product use. 4 (“S4”) Request: Minimal system impact; includes feature requests and other non-critical questions ▪ No Customer business impact ▪ Requests for enhancements by Customer

Appears in 1 contract

Samples: Support Agreement

Software Error Severity Classifications. All Software Errors shall be classified by RSA as follows: Error Severity Definition Examples 1 (“S1”) Critical: Severe problem preventing Customer or workgroup from performing critical business functions Production System data corruption (data loss, data unavailable) Production System system crash or hang Production Systems significantly impacted, such as severe performance degradation Production System and/or data is at high risk of potential loss or interruption Production System workaround is required immediately Time critical Production cutover impacted 2 (“S2”) High: Customer or workgroup able to perform job function, but performance of job function degraded or severely limited Production System adversely impacted Non-Production System data corruption (data loss, data unavailable) Non-Production System crash or hang Non-Production System and/or data is at high risk of potential loss or interruption Non-Production System workaround is required immediately Development system(s) is inoperative 3 (“S3”) Medium: Customer or workgroup performance of job function is largely unaffected Production or development system has encountered a non- critical problem or defect and/or questions have arisen on product use. 4 (“S4”) Request: Minimal system impact; includes feature requests and other non-critical questions No Customer business impact Requests for enhancements by Customer

Appears in 1 contract

Samples: Maintenance Agreement

AutoNDA by SimpleDocs

Software Error Severity Classifications. All Software Errors shall be classified by RSA NetWitness as follows: Error Severity Definition Examples 1 (“S1”) Critical: Severe problem preventing Customer or workgroup from performing critical business functions ▪ Production System data corruption (data loss, data unavailable) ▪ Production System crash or hang ▪ Production Systems significantly impacted, such as severe performance degradation ▪ Production System and/or data is at high risk of potential loss or interruption ▪ Production System workaround is required immediately ▪ Time critical Production cutover impacted 2 (“S2”) High: Customer or workgroup able to perform job function, but performance of job function degraded or severely limited ▪ Production System adversely impacted ▪ Non-Production System data corruption (data loss, data unavailable) ▪ Non-Production System crash or hang ▪ Non-Production System and/or data is at high risk of potential loss or interruption ▪ Non-Production System workaround is required immediately ▪ Development system(s) is inoperative 3 (“S3”) Medium: Customer or workgroup performance of job function is largely unaffected ▪ Production or development system has encountered a non- critical problem or defect and/or questions have arisen on product use. 4 (“S4”) Request: Minimal system impact; includes feature requests and other non-critical questions ▪ No Customer business impact ▪ Requests for enhancements by Customer

Appears in 1 contract

Samples: Maintenance Agreement for Netwitness Products

Time is Money Join Law Insider Premium to draft better contracts faster.