The modeling effort can be broken in four phases: 1. Getting to know the system being modeled, the different ways it can fail, and how the failures manifest themselves (symptoms, error-codes, tests). 2. Capturing the relationships in the TEAMS tool (the actual modeling). 3. Adding ref
Diagnosis is the process of determining the system health from observed effects. Typically, over 50% of the cases, the corrective action can be diagnosed unambiguously by reasoning on the presence and absence of error codes. For those cases, troubleshooting can be completely eliminate
Most service organizations do not make optimal use of available information to diagnose the problem. For example, presence of multiple error codes can actually help narrow down the set of possible suspects, but trying to document all such combinations is nearly impossible due to its c