UNDERSTAND THE CONCEPT
A symptom is what was observed, such as a leak or trip. A failure mode describes how the item failed to perform its function. A cause explains why it happened and may require investigation. Treating these as the same field makes trend analysis unreliable.
Use a short controlled vocabulary with equipment-specific choices and an explicit unknown option. Let technicians describe observations without forcing an unsupported root cause. Review frequently used other codes and preserve the supporting investigation when a cause is later confirmed.
Questions to take back to your team
- Do the fields distinguish observation from cause?
- Can users honestly record unknown?
- Who maintains the code list and reviews ambiguous entries?
Further reading
Explore the primary references below. Requirements and applicability depend on your organization and jurisdiction.
