Configuration · Intermediate
Create Symptoms and Causes
Learn to create reusable symptoms and causes in ManWinWin Desktop, distinguishing an observed fault from its diagnosed cause. Build clear, consistent entries for later failure reporting.
In effective maintenance management, clearly distinguishing between a symptom (what is observed) and a cause (why it happened) is crucial for accurate failure analysis. This distinction enables precise diagnosis, leading to more effective corrective actions and improved asset reliability. ManWinWin Desktop provides structured fields to define these elements for consistent reporting.
Where it's available and step by step
Step by step in ManWinWin Desktop
- 1
Open the Symptoms table in ManWinWin Desktop.
- 2
Review the existing symptoms to check whether the observation you want to register already has an equivalent entry.
- 3
Start a new symptom using New and enter a clear description of the observation, such as “Unusual vibration”, without including an assumed cause.
- 4
Save the symptom and confirm that it appears in the Symptoms table.
- 5
Open the Causes table and check whether the intended cause, such as “Bearing wear”, already exists.
- 6
If it does not exist, start a new cause using New and enter a technical description that identifies the cause rather than repeating the symptom.
- 7
Save the cause and confirm that it appears in the Causes table.
- 8
Review both entries to confirm that the symptom describes the observation and the cause describes a possible explanation to select only when supported by diagnosis.
Theory and technical background
The Symptom-Cause Relationship in Maintenance
A symptom describes an observable deviation from normal operating conditions, like 'unusual vibration' or 'leakage'. It's the 'what' of the failure. A cause, conversely, is the root reason for that symptom, such as 'bearing wear' or 'seal degradation'. It's the 'why'. Proper categorization ensures that technicians accurately report issues and engineers can conduct meaningful root cause analysis, a cornerstone of reliability-centered maintenance (RCM) and ISO 55000 asset management principles.
Standardization for Data Quality and Analysis
Standardizing symptoms and causes within a CMMS like ManWinWin is vital for data integrity. Consistent terminology across all maintenance records allows for accurate aggregation of failure data. This consistency is essential for calculating key performance indicators (KPIs) like Mean Time Between Failures (MTBF) and for identifying recurring failure patterns. Without standardized entries, data becomes noisy, hindering effective trend analysis and strategic decision-making regarding asset health and maintenance strategies.
Impact on Corrective and Preventive Maintenance
Precise symptom and cause recording directly impacts the effectiveness of both corrective and preventive maintenance. For corrective actions, a clear cause diagnosis guides the technician to the correct repair. For preventive maintenance, identifying common causes allows for the development of targeted inspection routes or scheduled replacements to avert future failures. This systematic approach contributes to optimizing asset availability and reducing downtime, aligning with EN 13306 definitions for maintenance terms.
Best practices
- Keep symptoms descriptive of the observation, not a diagnosis. E.g., 'High temperature' vs. 'Fan failure'.
- Ensure causes are technical explanations, not repetitions of symptoms. E.g., 'Bearing wear' not 'Vibration'.
- Avoid vague terms. Use specific, measurable language for both symptoms and causes.
- Regularly review and update your symptom and cause lists to reflect new assets or failure modes.
Frequently asked questions
Why separate symptoms from causes?
Separating symptoms (what is observed) from causes (why it happened) enhances diagnostic accuracy. It ensures that the initial report details the observable fault, while the subsequent diagnosis identifies the actual root problem, preventing misinterpretation and improving repair effectiveness.
Can one symptom have multiple causes?
Yes, absolutely. A single symptom like 'unusual noise' could be caused by various underlying issues, such as 'worn bearing', 'loose component', or 'improper lubrication'. This is why the diagnosis step is critical to pinpoint the actual cause.
How does this improve reporting accuracy?
By providing predefined lists, technicians use consistent terminology. This standardization eliminates ambiguity, makes data easier to analyze for trends, and ensures that everyone involved in maintenance operations understands and reports failures uniformly, improving overall data quality.
Need help with this topic?
Sign in with your company's ManWinWin API and user to request technical support followed by the ManWinWin team.
Back to Winston Help Center
Ask Winston or explore other lessons.