TEAMS-Designer

For TEAMS-Designer, the installation wizard will prompt the user to select from either installing the software for a single-user (curently logged in user) or for all users on the host machine.  If the user selects to install for a single-user then they do not need administrative privileges.  On the other hand, if TEAMS-Designer is to be installed for all users on the host computer then administrative privileges are required for the installation.

TEAMATE

TEAMATE does not require administrative privileges.

TEAMS-RDS

TEAMS-RDS requires administrative privileges in order to install it on a Windows Server 2003 and up.  A database administrator is also required to install the TEAMS-RDS database.

When QSI sends you your software license information, it also includes the expiration date of the license.  The expiration date information is also available within our software products.

For TEAMS-Designer and TEAMATE, go to “Help -> About <product-name>…” to view support and licensing information.  The licensing information is displayed on the bottom-left corner of the dialog.

In TEAMS-RDS, administrators may check the expiration date by clicking on the “Powered by RDS” link located on the bottom-left of the TEAMS-RDS page.  Select the license information tab to view the expiration date of your license.

The easiest way to activate your copy of TEAMS software is via the internet.  If the computer does not have internet access, you may also activate the software license by e-mail using another computer.  You will need a license id and password to activate your software, if you need a license and password please contact li*****@*****si.com.

Internet Activation

To activate your product, either launch the product from the start menu or launch the “Activate/Update” utility located in the same Start menu folder.  You will be prompted by a dialog wizard that will help you activate your product, just follow the steps below:

1. Select “Activate <product-name>”.
2. Next select “Activate <product-name> Online”.
3. Enter the license id and password provided by QSI and click on Continue.
4. If the activation is successful, the progress bar will turn green.  Click on continue to launch the product.

For your convenience, the same procedure is used to activate TEAMS-Designer, TEAMS-RDS and TEAMATE.

E-mail Activation

If the host computer does not have internet access, follow the steps below to activate your product:

1. Launch the product executable or “Activate/Update” utility from the Start menu.
2. Select “Activate <product-name>”.
3. Select “Activate Manually”.
4. Enter the license id and password provided by QSI and click on Continue.
5. Write down the two user codes displayed on the screen.  Log in to a computer that does have e-mail access and send the two user codes with your license id and passwors to li*****@*****si.com.  You may alternatively go to https://secure.softwarekey.com/solo/unlock/ and enter your user information here to generate the two activation codes.
6. Once you have acquired the two activation codes, enter them in the two fields provided and click on Continue.
7. If you have succesfully entered the two correct codes, the progress bar will turn green.  Click on Continue to finish.

To download our software, follow the steps below:

1. Select “Customer Portal” from the menu located on the top of our web site.
2. Enter your user name and password in the login page.
3. A drop-down menu listing the products you currently have access to will appear.  Select the product you wish to download.
4. Carefully read the license agreement and select “accept” in the drop-down box if you agree with the license agreement.
5. Click on “download” and save the file to your computer.

Note

If you do not have a user name and password, click on “Register” to apply for a user name and password.  At the registration page, enter your desired user name and your e-mail address to receive your password.

TEAMS-RT may be configured in two ways: as a server or as an embedded library (static, shared or dynamically linked) that client applications may directly interface.  In the first configuration, the TEAMS-RT server runs as a component on the TEAMS-RDS server.   The TEAMS-RT server has the advantage of logging the system status in the TEAMS-RDS server and allowing for managers to monitor the status of their systems on-line.  The embedded version of TEAMS-RT has a small footprint and is supported on a larger set of platforms.  The following table lists the operating systems supported by TEAMS-RT.

Periodically (once a day, or once a week, or any other custom user specified intervals) TEAMS-RDS server will automatically extract all the models that are mapped to systems in the “Production” state. In addition, an administrator may manually start the extraction process on demand. The extracted TEAMATE files are exported into a repository location that can be set by a TEAMS-RDS administrator. There are three ways for TEAMATE users to obtain the models from the TEAMS-RDS server and store their session logs for TEAMS-RDS to consume:

• File Location: The TEAMATE files and session logs may be stored on seperate folders on a shared network drive.
• HTTP(s): The TEAMS-RDS server can serve the TEAMATE files via HTTP(s).
• FTP Service: TEAMS-RDS server can store/access the TEAMATE files and session logs from a FTP server.

Note

In a default installation, TEAMS-RDS serves its TEAMATE files via HTTP through the tomcat server that is installed with the installation.

Conventional methods of measuring the duration of an outage start the clock when the problem is first reported to the vendor or Call Center. The clock stops when the technician logs that the problem is resolved.  In reality, however, the outage really starts the moment the system has an interrupt or stops working. With “Enhanced Service Coverage View”, the TEAMS system can detect problems at or even before the moment of outage, so that corrective actions can occur almost immediately. On the back end of the timeline, TEAMS can also run system verification tests to ensure the instrument is 100% fixed before it is returned to service. Click here to see an illustration of the difference between Conventional and Enhanced Service Coverage.

By default a test is assigned two outcomes, a pass outcome and a fail outcome.  To add further outcomes to a test, select the Functions tab in the test-point properties panel.  Click on the Edit button that is next to the Outcome Name drop-down list.  A dialog with a list of outcomes attached to the test will be displayed.  To add another outcome to the test, just click on the Add button and enter the name of the new outcome.  The outcome will be added to the bottom of the list, making it a fail outcome.  To make it the pass outcome of the test, select it and use the up arrow to move it to the top of the list.  Keep in mind that a test only has one pass outcome and one or more fail outcomes.

Notes:

• The first outcome in the outcome list is always the pass outcome and the rest are fail outcomes.
• A test may have up to eight fail outcomes.

Case Based or Knowledge based solutions require some form of history or prior service knowledge as they try to retrieve “best known solutions”. However, these are solutions that are known best (because they were documented by service agents or experts) but are not necessarily the best or optimal solutions. Further, they are typically not good at providing the single right solution for a particular problem, instead providing a list of close matches for similar problems. To make things worse, these close matches are ranked by frequency of occurrence, implying a difficult but rare problem where the service agent needs most help is invariably at the bottom of the list, and the most common solutions that every service agent is familiar with is ranked at the top.  They tend to promote solving problems by trial and error, and may increase cost of service over the long run.

QSI TEAMS applies logic to solve troubleshooting problems. QSI TEAMS does not past service history or documented cases. It excels when an error or symptom has many causes or faults manifest into many symptoms. It can be deployed at the machine level, the call center, the field or automatically from machine to machine (M2M).

To understand how TEAMS works, think of your GPS navigation system. It is great for visiting places you never been before! And it is also great at finding the optimal route for that day, given the road and traffic conditions. The GPS and TEAMS solution share two important attributes: it applies algorithms or logic to solve new problems (instead of trying to utilize past experience or solutions), and it recognizes yesterday’s solution might not be the best solution today.

Taking the analogy further, think of the GPS software as the TEAMS reasoner, and the maps are the cause-effect relationships – i.e., which faults trigger with error code or test failure – in your system. The TEAMS reasoner applies logic and optimization algorithms to rule-in and rule-out possible causes and guides the technician through additional information gathering, until it determines the root cause. It then guides the service agent through the corrective action and the verification steps, all the while logging each of the steps automatically, and learning from it. Just like the GPS can route you through various options (e.g., avoid toll roads or ferries), the TEAMS reasoner can guide service agents with different levels of skills, certifications, support equipment — generating a different troubleshooting path based in his or her ability.

Simply put, it is the kind of technology that helps a 19 year old kid fix a F16!

To update a system’s revision:

1. Log in using a user with the “supervisor” role assigned.
2. Select Create/Delete Systems from the left menu.
3. Select the system under the System column.
4. The system’s properties will be displayed. Select the new revision from the Model Revision drop-down list.
5. Click on Modify to update the system’s revision.

Note:

• A system may only be updated to a later revision of the model.