There are many reasons why a test may not be used for diagnosis, lets begin by looking at a diagnostic session. A diagnostic session has three basic phases: the acceptance phase, the diagnosis phase and the operation check phase. Each phase has a set of viable tests that may be used during the session. These phases may sound familiar because a test’s type may be: test, symptom, operational check and acceptance test. Depending on the test’s type, it may or may not be used in the diagnostic session. A test will be added to a set if the test’s type for that particular set is enabled. For example if a test is marked as a Operational Check test it will be added to the set of viable tests used during the operational check phase.
Tests that are marked as symptoms appear in the beginning of a diagnostic session. Tests marked only as “symptom” will not be used in any of the phases.
Notes:
Prior to TEAMS-Designer 11.5, tests that were marked other than type “Test” were also included in the diagnostic phases. This behavior has been changed as described above. To retain a model’s diagnostic tree, ensure all of the tests are of type “Test” as well.
Before proceeding you will need to know the following information to configure the ODBC data source, contact your IT administrator for assistance.
Prerequisites:
To add a MSSQL ODBC data source:


Note:
Before proceeding you will need to know the following information to configure the ODBC data source, contact your IT administrator for assistance.
Prerequisites:
Before continuing, make sure you have the MySQL ODBC driver installed in your computer. If not, click here and install the appropriate driver for your operating system. For example, if are running 64-bit version of TEAMS-Designer download and install mysql-connector-odbc-5.x.x-winx64.msi. If you are running 32-bit version of TEAMS-Designer download and install mysql-connector-odbc-5.x.x-win32.msi.
To add a MySQL ODBC data source:


Tips:
Function-mappings consists of a single destination function and one or more source functions. A function-mapping will be applied if any of the source functions defined in a function-mapping reach any of the input ports of a failure mode and are not being blocked. For example, if a function-mapping defines three source functions then any of the three functions will be mapped to the destination function. The mapped function will be propagated to all the output ports of the failure mode.
Tips:
When computing function propagation, blockers are applied first and then function mappings are applied. For example, if function-1 is blocked and is also defined in a function mapper as a source function, TEAMS-Designer will not apply the function mapper to the already blocked function.
To remove a function mapper in a module:
Note: Only one function mapper may be removed at a time.
Yes it is possible to add your own hierachy labels. Just open the module’s properties panel and enter the new hierarchy label in the combo-box. Click Ok to apply the changes. The hierachy label will be added to the bottom of the list next time the drop-down list is displayed.
Hint: To add the new hierarchy label to multiple modules, open the module batch editor and apply it to all the applicable modules.
To generate a dependency matrix report, simply go to Tools -> Options…, enable the Generate D-Matrix Spreadsheet Report option then go to Analysis -> Testability Analysis… or Analysis -> Serviceability Analysis…, depending on your license.
TEAMS-Designer will generate a CSV and Microsoft Excel file containing the dependency matrix. The files are located in the REPORTS sub-folder under the model’s folder. The REPORTS folder contains a list of time-stamp folders for each analysis completed. TEAMS-Designer creates a file formatted using the following convention <model_name>_D-Matrix.xls in each folder.
If the Mapped functions button is not visible, go to Tools -> Options… and enable Use Mapping and Blocking Functions option. If the button is greyed out, it means that the module is not a failure mode (lowest-level module). Only failure modes may have function mappers and blockers defined.
The best way to send a model to someone is to export it as a xml file. Open the model and click on File -> Export Model as XML File. The model will be saved as a compressed archieve using the tmsx extension. An alternative approach is to compress the model’s folder using a compression utility. Just remember to un-compress before opening with TEAMS-Designer.
Notes:
