- About Us
When creating a model, the individual subassemblies are created as modules. The models of these modules can be shared with little or no modification across multiple systems. This means that if a subassembly is shared across multiple systems, it only needs to be modeled once. Thus, the models are nearly as reusable as the underlying system components!
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 reference material and instructions on how to perform individual steps of troubleshooting.
4. Verification and validation of the diagnosis and troubleshooting strategy generated by the reasoner.
Different customers take different amount of time at the various steps — especially since some of the steps are related to how well the organization captures and documents knowledge, and how accessible the information is to the modeler. Based on our experience, a typical system takes one or two man-months to model. As a rule of thumb, each test or fault takes one hour to model, and therefore, a typical system with up to three hundred error codes and manual tests will take under 2 person-months.
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 knowledgeable with how the system works is usually a better candidate to model. We can supply you with a good job description if needed.