Severity Assessment Worksheet

V3 Neo β€” Axis Bank DLF Moti Nagar  |  Review S / O / D, add comments & test cases, export to Excel

Severity (S) β€” How bad if it happens?

10Hazardous without warning. Safety risk, or complete site shutdown with no fallback.
9Hazardous with warning. Site down extended. Data breach risk (wrong bin in bank).
8Very high. System inoperable, partial workaround exists. Major customer impact.
7High. Degraded performance, significant delays. Robot must return to dock.
6Moderate. Single task aborted, system recovers automatically. Noticeable to bank staff.
5Low-moderate. Slight delay, task retried successfully. Customer may notice.
4Low. Minor degradation, auto-recovery. Customer unlikely to notice.
3Very low. Cosmetic or logging issue. No operational impact.
2Slight. Barely perceptible. Only visible in diagnostic logs.
1None. No effect on system or customer.

Occurrence (O) β€” How often will it happen?

10Almost certain. >1 in 5 cycles. Known design flaw or proven failure pattern.
9Very high. 1 in 5–10 cycles. Seen consistently in V3 field data across multiple sites.
8High. 1 in 10–20 cycles. Recurring V3 field issue, fix not verified in Neo.
7Moderately high. 1 in 20–50 cycles. Seen at 5+ V3 sites. Architecture-level issue.
6Moderate-high. 1 in 50–100 cycles. Seen at 3+ V3 sites. New hardware limited test hours.
5Moderate. 1 in 100–200 cycles. Occasional field reports. New component, bench tested.
4Low-moderate. 1 in 200–500 cycles. Infrequent. Design change addresses known issue.
3Low. 1 in 500–2,000 cycles. Rare field reports. Mature component with track record.
2Very low. 1 in 2,000–10,000 cycles. Almost never seen. Well-proven design.
1Remote. <1 in 10,000 cycles. Theoretically possible, never observed.

Detection (D) β€” Can we catch it before impact?

10No detection. No sensor or test can identify the failure before customer impact.
9Almost undetectable. Only discovered after failure cascades.
8Very low. Post-event analysis only. No real-time monitoring.
7Low. Silent failure β€” system appears normal. Requires specific diagnostic query.
6Low-moderate. Detected eventually with significant delay.
5Moderate. Sensor exists but may miss edge cases. Specific test scenario needed.
4Moderately high. System sensor + FMS monitoring detects within seconds.
3High. Multiple redundant sensors. Operator notices immediately. Clear FMS error state.
2Very high. Continuous automated monitoring catches it instantly. Auto-recovery triggers.
1Almost certain. Physical interlock prevents failure. Hardwired safety system.
β‰₯200
Critical β€” blocks go-live
100–199
P1 β€” must mitigate
50–99
Watch during commissioning
<50
Acceptable β€” document
Phase
Legend: S/O/D changed from baseline RPN β‰₯200 Critical RPN 100–199 P1 RPN 50–99 Watch RPN <50 Acceptable All edits auto-save to browser. Click Save or Export when done.
ID Process Step Failure Mode S O D RPN
(new)		 Ξ” vs
Baseline		 Owner Recommended Action (from PFMEA) Comments / Test Results (free text) Test Case Add-ons & Additional Failure Cases (free text)
βœ“ Saved to browser storage