A TEAMS model captures the many-to-many mapping between causes (things that fail, i.e., faults) and effects (things that detect failures, i.e., tests and symptoms). If you know these relationships, you can import them in as a spreadsheet. Otherwise, you lay out the system and its inte
QSI TEAMS is a model based approach, as opposed to experience, history or case based (all of which require accurate legacy data). QSI TEAMS does not require legacy data. It can produce accurate results immediately. It excels when an error or symptom has many causes or faults manifest
While the system experts may be good at solving problems, they are not necessarily the best choice to model. They tend to model solutions (to specific problems or symptoms) and not the problem space (i.e., what fails, how you detect failures and their relationships). Someone who is kn
