FMEA Risk Probability Filtering – Workaround for Numeric ‘Greater-Than’ Logic

Amanda Jennewein
Amanda Jennewein
  • Updated

Published Date: June 17, 2025

Validated: Yes

Audience: Everyone

Products and Versions Covered:

  • Jama Connect® 

Summary

Identify high-risk FMEA items whose calculated Risk Probability or RPN exceeds a threshold. Because Jama Connect treats numeric fields as strings, standard “> / <” operators cannot be used in filters.

To work around this limitation:

  • Convert numeric risk outputs into enumerated categories (Low / Medium / High), or

  • Build a custom string-equality filter that includes all values above the threshold.

Document this limitation in the control plan and, for audit readiness, ensure that reviewers always run the approved filter before sign-off.

Resolution

Step Action Result / Notes
1 Define Threshold – e.g., RPN > 100. Establish review trigger.
2 Enumerate Valid High Values – 105, 110, 125, 150 … Required for string filter.
3 Create FilterProjects ▶ List View ▶ Create Filter• Match Any of the following• Field Risk Probability = 105, 110, 125, 150 … Simulates “greater than.”
4 Save as FMEA – High Risk Probability. All users run same filter.
(Preferred Long-Term) Replace numeric RPN field with Risk Level picklist (“High / Med / Low”). Auto-calculate externally, then import value. One filter clause ➔ scalable.
5 Review & Escalate – run filter prior to design reviews; export list for compliance file. Ensures high-risk items receive mitigation.

Limitation: Any new numeric value above the threshold must be manually added to the filter until Jama supports numeric comparisons.

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.